RequirementsMac OS X
Date addedJun 06, 2018
SQLite for Mac is a in-process library which implements a self indulgent, serverless, zero-configuration, transactional SQL database engine. The code for SQLite is from the public domain and can be free to be used for any use, private or commercial. SQLite is arguably the most frequently deployed database on the planet with more software than we could count, including many high-profile jobs.
Complete SQL execution with innovative features like partial indicators and common table expressions. (Omitted attributes )
A complete database is stored in one cross-platform disk . Perfect for use within an application file format. (Watch limits.html.)
Small code footprint: less than 500KiB completely configured or less with optional attributes omitted.
Composed in ANSI-C. TCL bindings included. Bindings for heaps of different languages available individually.
Well-commented source code with 100% division evaluation policy.
Available as one ANSI-C source-code document that's not difficult to compile and therefore isn't hard to incorporate into a bigger project.
Self-contained: no external dependencies.
Cross-platform: Android, *BSD, iOS, Linux, Mac, Solaris, VxWorks, and Windows (Win32, WinCE, WinRT) are supported from the box. Easy to port to other programs.
Sources are in the public domain. Use for any purpose.
Has a standalone command-line interface (CLI) client which may be employed to manage SQLite databases.
Add support for PostgreSQL-style UPSERT
Add support for auxiliary columns in r-tree tables
Add C-language APIs for discovering SQL keywords used by SQLite: sqlite3_keyword_count(), sqlite3_keyword_name(), and sqlite3_keyword_check()
Add C-language APIs for dynamic strings based on the sqlite3_str object
Enhance ALTER TABLE so that it recognizes "true" and "false" as valid arguments to DEFAULT
Add the sorter-reference optimization as a compile-time option. Only available if compiled with SQLITE_ENABLE_SORTER_REFERENCES
Improve the format of the EXPLAIN QUERY PLAN raw output, so that it gives better information about the query plan and about the relationships between the various components of the plan
- Added the SQLITE_DBCONFIG_RESET_DATABASE option to the sqlite3_db_config() API
Automatically intercepts the raw EXPLAIN QUERY PLAN output and reformats it into an ASCII-art graph
Lines that begin with "#" and that are not in the middle of an SQL statement are interpreted as comments
Added the --append option to the ".backup" command
Added the ".dbconfig" command
UPDATE avoids writing database pages that do not actually change. For example, "UPDATE t1 SET x=25 WHERE y=?" becomes a no-op if the value in column x is already 25. Similarly, when doing UPDATE on records that span multiple pages, only write the subset of pages that contain the changed value(s)
Queries that use ORDER BY and LIMIT now try to avoid computing rows that cannot possibly come in under the LIMIT. This can greatly improve performance of ORDER BY LIMIT queries, especially when the LIMIT is small relative to the number of unrestricted output rows
The OR optimization is allowed to proceed even if the OR expression has also been converted into an IN expression. Uses of the OR optimization are now also more clearly shown in the EXPLAIN QUERY PLAN output
The query planner is more aggressive about using automatic indexes for views and subqueries for which it is not possible to create a persistent index
Make use of the one-pass UPDATE and DELETE query plans in the R-Tree extension where appropriate
Performance improvements in the LEMON-generated parser
For the right-hand table of a LEFT JOIN, compute the values of expressions directly rather than loading precomputed values out of an expression index as the expression index might not contain the correct value. Ticket 7fa8049685b50b5aeb0c2
Do not attempt to use terms from the WHERE clause to enable indexed lookup of the right-hand table of a LEFT JOIN. Ticket 4ba5abf65c5b0f9a96a7a
Fix a memory leak that can occur following a failure to open error in the CSV virtual table
Fix a long-standing problem wherein a corrupt schema on the sqlite_sequence table used by AUTOINCREMENT can lead to a crash. Ticket d8dc2b3a58cd5dc2918a1
Fix the json_each() function so that it returns valid results on its "fullkey" column when the input is a simple value rather than an array or object