A lightweight SQLite wrapper and ORM for Swift 4.x, enabling direct database access and automatic table creation.
SQLiteDB is a lightweight SQLite wrapper and ORM for Swift 4.x that simplifies database interactions by providing direct SQL access and an object-relational mapping layer. It allows developers to execute queries with parameter binding and manage database tables using Swift classes, reducing the need for boilerplate SQL code. The library supports both pre-loaded databases and automatic table creation, making it versatile for various application needs.
Swift developers building iOS or macOS applications that require local data persistence with SQLite, particularly those seeking a simple, ORM-like interface without heavy dependencies.
Developers choose SQLiteDB for its simplicity, lightweight design, and seamless integration with Swift, offering both low-level SQL control and a convenient ORM layer. Its automatic schema management and support for multiple database instances reduce development overhead compared to raw SQLite usage.
Basic SQLite wrapper for Swift 4.x and lightweight ORM for accessing underlying tables in an SQLite database
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports parameter binding in SQL queries, preventing SQL injection and enhancing security, as demonstrated in the usage examples for safe query execution.
The SQLTable class allows modeling database tables as Swift classes, reducing boilerplate code for CRUD operations without heavy dependencies.
Automatically creates and updates database tables based on class properties, simplifying development iterations, as noted in the SQLTable usage section.
Supports both pre-loaded database files and dynamic creation at runtime, offering versatility for different application needs, per the adding to project instructions.
Lacks features for complex relationships, transactions, and advanced migrations, focusing only on basic CRUD operations, which may require manual SQL for sophisticated queries.
Recent updates changed method names (e.g., openDB to open) and row numbering from 1-based to 0-based, as warned in the README, potentially breaking existing code without seamless migration paths.
Cloud database functionality is explicitly marked as not ready for production in the README update note, limiting its use for synced or distributed data scenarios.