SQLite 3.8.9

SQLite is a lightweight and embeddable database. It's fully ACID and SQL92 compliant with 100% test coverage. As storage a single cross-platform disk file format is used, which may be up to terrabytes in size. It requires no setup and little administrative work. SQLite itself has a simple yet expandable API. Bindings for most programming languages exist on all major plattforms.

Tags c sql database sqlite embedded
License Public Domain
State stable

Homepage Download

Recent Releases

3.8.910 Apr 2015 01:45 feature: Add VxWorks-7 as an officially supported and tested platform. Added the sqlite3_status64() interface. Fix memory size tracking so that it works even if SQLite uses more than 2GiB of memory. Added the PRAGMA index_xinfo command. Fix a potential 32-bit integer overflow problem in the sqlite3_blob_read() and sqlite3_blob_write() interfaces. Ensure that prepared statements automatically reset on extended error codes of SQLITE_BUSY and SQLITE_LOCKED even when compiled using SQLITE_OMIT_AUTORESET. Correct miscounts in the sqlite3_analyzer.exe utility related to WITHOUT ROWID tables. Added the ".dbinfo" command to the command-line shell. Improve the performance of fts3/4 queries that use the OR operator and at least one auxiliary fts function.
3.8.8.326 Feb 2015 22:05 feature: Fix a bug that can lead to incorrect results if the qualifying constraint of a partial index appears in the ON clause of a LEFT JOIN.
3.8.8.231 Jan 2015 07:25 minor bugfix: Fix a bug in the sorting logic, present since version 3.8.4, that can cause output to appear in the wrong order on queries that contains an ORDER BY clause, a LIMIT clause, and that have approximately 60 or more columns in the result set.
3.8.8.121 Jan 2015 10:45 feature: Fix a bug in the sorting logic, present since version 3.8.4, that can cause output to appear in the wrong order on queries that contains an ORDER BY clause, a LIMIT clause, and that have approximately 60 or more columns in the result set.
3.8.817 Jan 2015 16:25 feature: Added the PRAGMA data_version command that can be used to determine if a database file has been modified by another process. Added the SQLITE_CHECKPOINT_TRUNCATE option to the sqlite3_wal_checkpoint_v2() interface, with corresponding enhancements to PRAGMA wal_checkpoint. Added the sqlite3_stmt_scanstatus() interface, available only when compiled with SQLITE_ENABLE_STMT_SCANSTATUS. The sqlite3_table_column_metadata() is enhanced to work correctly on WITHOUT ROWID tables and to check for the existence of a a table if the column name parameter is NULL. The interface is now also included in the build by default, without requiring the SQLITE_ENABLE_COLUMN_METADATA compile-time option. Added the SQLITE_ENABLE_API_ARMOR compile-time option. Added the SQLITE_REVERSE_UNORDERED_SELECTS compile-time option. Added the SQLITE_SORTER_PMASZ compile-time option and SQLITE_CONFIG_PMASZ start-time option. Added the SQLITE_CONFIG_PCACHE_HDRSZ option to sqlite3_config() which makes it easier for applications to determine the appropriate amount of memory for use with SQLITE_CONFIG_PAGECACHE. The number of rows in a VALUES clause is no longer limited by SQLITE_LIMIT_COMPOUND_SELECT. Added the eval.c loadable extension that implements an eval() SQL function that will recursively evaluate SQL. Performance Enhancements: Reduce the number of memcpy() operations involved in balancing a b-tree, for 3.2 overall performance boost. Improvements to cost estimates for the skip-scan optimization. The automatic indexing optimization is now capable of generating a partial index if that is appropriate. Bug fixes: Ensure durability following a power loss with PRAGMA journal_mode=TRUNCATE" by calling fsync() right after truncating the journal file. The query planner now recognizes that any column in the right-hand table of a LEFT JOIN can be NULL, even if that column has a NOT NULL constraint. Avoid trying to optimize out NULL tests in those cases. Fix for ticket 6f2222d550f5b0ee7ed. Make sure ORDER BY
3.8.7.412 Dec 2014 12:25 feature: This release fixes adds in a mutex that is required by the changes of the 3.8.7.3 patch but was accidently omitted. The mutex was not required by any of the internal SQLite tests, but Firefox crashes without it. Test cases have been added to ensure that mutex is never again missed.
3.8.7.308 Dec 2014 20:05 feature: Bug fix: Ensure the cached KeyInfo objects (an internal abstraction not visible to the application) do not go stale when operating in shared cache mode and frequently closing and reopening some database connections while leaving other database connections on the same shared cache open continuously. Ticket e4a18565a36884b00edf.
3.8.7.220 Nov 2014 03:19 feature: Enhance the ROLLBACK command so that pending queries are allowed to continue as long as the schema is unchanged. Formerly, a ROLLBACK would cause all pending queries to fail with an SQLITE_ABORT or SQLITE_ABORT_ROLLBACK error. That error is still returned if the ROLLBACK modifies the schema. Bug fix: Make sure that NULL results from OP_Column are fully and completely NULL and do not have the MEM_Ephem bit set. Bug fix: The c format in sqlite3_mprintf() is able to handle precisions greater than 70. Bug fix: Do not automatically remove the DISTINCT keyword from a SELECT that forms the right-hand side of an IN operator since it is necessary if the SELECT also contains a LIMIT.
3.8.7.130 Oct 2014 03:15 feature: In PRAGMA journal_mode=TRUNCATE mode, call fsync() immediately after truncating the journal file to ensure that the transaction is durable across a power loss. Fix an assertion fault that can occur when updating the NULL value of a field at the end of a table that was added using ALTER TABLE ADD COLUMN. Do not attempt to use the strchrnul() function from the standard C library unless the HAVE_STRCHRNULL compile-time option is set.
3.8.718 Oct 2014 03:17 feature: Many micro-optimizations result in 20.3 more work for the same number of CPU cycles relative to the previous release. The cumulative performance increase since version 3.8.0 is 61 . Measured using cachegrind on the speedtest1.c workload on Ubuntu 13.10 x64 with gcc 4.8.1 and -Os. Your performance may vary.) The sorter can use auxiliary helper threads to increase real-time response. This feature is off by default and may be enabled using the PRAGMA threads command or the SQLITE_DEFAULT_WORKER_THREADS compile-time option. Enhance the skip-scan optimization so that it is able to skip index terms that occur in the middle of the index, not just as the left-hand side of the index. Improved optimization of CAST operators. Various improvements in how the query planner uses sqlite_stat4 information to estimate plan costs. New Features: Added new interfaces with 64-bit length parameters: sqlite3_malloc64(), sqlite3_realloc64(), sqlite3_bind_blob64(), sqlite3_result_blob64(), sqlite3_bind_text64(), and sqlite3_result_text64(). Added the new interface sqlite3_msize() that returns the size of a memory allocation obtained from sqlite3_malloc64() and its variants. Added the SQLITE_LIMIT_WORKER_THREADS option to sqlite3_limit() and PRAGMA threads command for configuring the number of available worker threads. The spellfix1 extension allows the application to optionally specify the rowid for each INSERT. Added the User Authentication extension. Bug Fixes: Fix a bug in the partial index implementation that might result in an incorrect answer if a partial index is used in a subquery or in a view. Fix a query planner bug that might cause a table to be scanned in the wrong direction thus reversing the order of output) when a DESC index is used to implement the ORDER BY clause on a query that has an identical GROUP BY clause. Fix a bug in sqlite3_trace() that was causing it to sometimes fail to print an SQL statement if that statement needed to be re-prepared. Fix a faulty assert() st
3.8.616 Aug 2014 03:15 feature: Added support for hexadecimal integer literals in the SQL parser. Ex: 0x123abc) Enhanced the PRAGMA integrity_check command to detect UNIQUE and NOT NULL constraint violations. Increase the maximum value of SQLITE_MAX_ATTACHED from 62 to 125. Increase the timeout in WAL mode before issuing an SQLITE_PROTOCOL error from 1 second to 10 seconds. Added the likely(X) SQL function. The unicode61 tokenizer is now included in FTS4 by default. Trigger automatic reprepares on all prepared statements when ANALYZE is run. Added a new loadable extension source code file to the source tree: fileio.c Add extension functions readfile(X) and writefile(X,Y) using code copy/pasted from fileio.c in the previous bullet) to the command-line shell. Added the .fullschema dot-command to the command-line shell. Performance Enhancements: Deactivate the DISTINCT keyword on subqueries on the right-hand side of the IN operator. Add the capability of evaluating an IN operator as a sequence of comparisons as an alternative to using a table lookup. Use the sequence of comparisons implementation in circumstances where it is likely to be faster, such as when the right-hand side of the IN operator is small and/or changes frequently. The query planner now uses sqlite_stat4 information (created by ANALYZE) to help determine if the skip-scan optimization is appropriate. Ensure that the query planner never tries to use a self-made transient index in place of a schema-defined index. Other minor tweaks to improve the quality of VDBE code. Bug Fixes: Fix a bug in CREATE UNIQUE INDEX, introduced when WITHOUT ROWID support added in version 3.8.2, that allows a non-unique NOT NULL column to be given a UNIQUE index. Fix a bug in R-Tree extension, introduced in the previous release, that can cause an incorrect results for queries that use the rowid of the R-Tree on the left-hand side of an IN operator. Fix the sqlite3_stmt_busy() interface so that it gives the correct answer for ROLLBAC
3.8.512 Jul 2014 21:30 major feature: Added support for partial sorting by index. Enhance the query planner so that it always prefers an index that uses a superset of WHERE clause terms relative to some other index. Improvements to the automerge command of FTS4 to better control the index size for a full-text index that is subject to a large number of updates. Added the sqlite3_rtree_query_callback() interface to R-Tree extension. Added new URI query parameters "nolock" and "immutable". Use less memory by not remembering CHECK constraints on read-only database connections. Enable the OR optimization for WITHOUT ROWID tables. Render expressions of the form "x IN (?)" (with a single value in the list on the right-hand side of the IN operator) as if they where "x==?", Similarly optimize "x NOT IN (?)". Add the ".system" and ".once" commands to the command-line shell. Added the SQLITE_IOCAP_IMMUTABLE bit to the set of bits that can be returned by the xDeviceCharacteristics method of a VFS. Added the SQLITE_TESTCTRL_BYTEORDER test control. Bug Fixes: OFFSET clause ignored on queries without a FROM clause. Assertion fault on queries involving expressions of the form "x IN (?)". Incorrect column datatype reported. Duplicate row returned on a query against a table with more than 16 indices, each on a separate column, and all used via OR-connected constraints. Partial index causes assertion fault on UPDATE OR REPLACE. Crash when calling undocumented SQL function sqlite_rename_parent() with NULL parameters. ORDER BY ignored if the query has an identical GROUP BY. The group_concat(x,'') SQL function returns NULL instead of an empty string when all inputs are empty strings. Fix a bug in the VDBE code generator that caused crashes when doing an INSERT INTO ... SELECT statement where the number of columns being inserted is larger than the number of columns in the destination table. Fix a problem in CSV import in the command-line shell where if the leftmost field of the first ro