Small. Fast. Reliable.

Choose any three. Home

Menu

About

Documentation

Download

License

Support

Purchase

Search About

Documentation

Download

Support

Purchase Search Documentation Search Changelog

Release History

This page provides a high-level summary of changes to SQLite. For more detail, see the Fossil checkin logs at http://www.sqlite.org/src/timeline and http://www.sqlite.org/src/timeline?t=release. See the chronology a succinct listing of releases.

2020-08-14 (3.33.0)

Support for UPDATE FROM following the PostgreSQL syntax. Increase the maximum size of database files to 281 TB. Extended the PRAGMA integrity_check statement so that it can optionally be limited to verifying just a single table and its indexes, rather than the entire database file. Added the decimal extension for doing arbitrary-precision decimal arithmetic. Enhancements to the ieee754 extension for working with IEEE 754 binary64 numbers. CLI enhancements: Added four new output modes: "box", "json", "markdown", and "table". The "column" output mode automatically expands columns to contain the longest output row and automatically turns ".header" on if it has not been previously set. The "quote" output mode honors ".separator" The decimal extension and the ieee754 extension are built-in to the CLI Query planner improvements: Add the ability to find a full-index-scan query plan for queries using INDEXED BY which previously would fail with "no query solution". Do a better job of detecting missing, incomplete, and/or dodgy sqlite_stat1 data and generates good query plans in spite of the misinformation. Improved performance of queries like "SELECT min(x) FROM t WHERE y IN (?,?,?)" assuming an index on t(x,y). In WAL mode, if a writer crashes and leaves the shm file in an inconsistent state, subsequent transactions are now able to recover the shm file even if there are active read transactions. Before this enhancement, shm file recovery that scenario would result in an SQLITE_PROTOCOL error. Hashes: SQLITE_SOURCE_ID: 2020-08-14 13:23:32 fca8dc8b578f215a969cd899336378966156154710873e68b3d9ac5881b0ff3f SHA3-256 for sqlite3.c: d00b7fffa6d33af2303430eaf394321da2960604d25a4471c7af566344f2abf9

2020-06-18 (3.32.3)

Various minor bug fixes including fixes for tickets 8f157e8010b22af0, 9fb26d37cefaba40, e367f31901ea8700, b706351ce2ecf59a, 7c6d876f84e6e7e2, and c8d3b9f0a750a529. Hashes: SQLITE_SOURCE_ID: 2020-06-18 14:00:33 7ebdfa80be8e8e73324b8d66b3460222eb74c7e9dfd655b48d6ca7e1933cc8fd SHA3-256 for sqlite3.c: b62b77ee1c561a69a71bb557694aaa5141f1714c1ff6cc1ba8aa8733c92d4f52

2020-06-04 (3.32.2)

Fix a long-standing bug in the byte-code engine that can cause a COMMIT command report as success when in fact it failed to commit. Ticket 810dc8038872e212 Hashes: SQLITE_SOURCE_ID: 2020-06-04 12:58:43 ec02243ea6ce33b090870ae55ab8aa2534b54d216d45c4aa2fdbb00e86861e8c SHA3-256 for sqlite3.c: f17a2a57f7eebc72d405f3b640b4a49bcd02364a9c36e04feeb145eccafa3f8d

2020-05-25 (3.32.1)

Fix two long-standing bugs that allow malicious SQL statements to crash the process that is running SQLite. These bugs were announced by a third-party approximately 24 hours after the 3.32.0 release but are not specific to the 3.32.0 release. Other minor compiler-warning fixes and whatnot. Hashes: SQLITE_SOURCE_ID: 2020-05-25 16:19:56 0c1fcf4711a2e66c813aed38cf41cd3e2123ee8eb6db98118086764c4ba83350 SHA3-256 for sqlite3.c: f695ae21abf045e4ee77980a67ab2c6e03275009e593ee860a2eabf840482372

2020-05-22 (3.32.0)

2020-01-27 (3.31.1)

Revert the data layout for an internal-use-only SQLite data structure. Applications that use SQLite should never reference internal SQLite data structures, but some do anyhow, and a change to one such data structure in 3.30.0 broke a popular and widely-deployed application. Reverting that change in SQLite, at least temporarily, gives developers of misbehaving applications time to fix their code. Fix a typos in the sqlite3ext.h header file that prevented the sqlite3_stmt_isexplain() and sqlite3_value_frombind() interfaces from being called from run-time loadable extensions. Hashes: SQLITE_SOURCE_ID: 2020-01-27 19:55:54 3bfa9cc97da10598521b342961df8f5f68c7388fa117345eeb516eaa837bb4d6 SHA3-256 for sqlite3.c: de465c64f09529429a38cbdf637acce4dfda6897f93e3db3594009e0fed56d27

2020-01-22 (3.31.0)

2019-10-10 (3.30.1)

Fix a bug in the query flattener that might cause a segfault for nested queries that use the new FILTER clause on aggregate functions. Ticket 1079ad19993d13fa Cherrypick fixes for other obscure problems found since the 3.30.0 release Hashes: SQLITE_SOURCE_ID: 2019-10-10 20:19:45 18db032d058f1436ce3dea84081f4ee5a0f2259ad97301d43c426bc7f3df1b0b SHA3-256 for sqlite3.c: f96fafe4c110ed7d77fc70a7d690e5edd1e64fefb84b3b5969a722d885de1f2d

2019-10-04 (3.30.0)

2019-07-10 (3.29.0)

Added the SQLITE_DBCONFIG_DQS_DML and SQLITE_DBCONFIG_DQS_DDL actions to sqlite3_db_config() for activating and deactivating the double-quoted string literal misfeature. Both default to "on" for legacy compatibility, but developers are encouraged to turn them "off", perhaps using the -DSQLITE_DQS=0 compile-time option. -DSQLITE_DQS=0 is now a recommended compile-time option. Improvements to the query planner: Improved optimization of AND and OR operators when one or the other operand is a constant. Enhancements to the LIKE optimization for cases when the left-hand side column has numeric affinity. Added the "sqlite_dbdata" virtual table for extracting raw low-level content from an SQLite database, even a database that is corrupt. Improvements to rounding behavior, so that the results of rounding binary numbers using the round() function are closer to what people who are used to thinking in decimal actually expect. Enhancements to the CLI: Add the ".recover" command which tries to recover as much content as possible from a corrupt database file. Add the ".filectrl" command useful for testing. Add the long-standing ".testctrl" command to the ".help" menu. Added the ".dbconfig" command Hashes: SQLITE_SOURCE_ID: 2019-07-10 17:32:03 fc82b73eaac8b36950e527f12c4b5dc1e147e6f4ad2217ae43ad82882a88bfa6 SHA3-256 for sqlite3.c: d9a5daf7697a827f4b2638276ce639fa04e8e8bb5fd3a6b683cfad10f1c81b12

2019-04-16 (3.28.0)

2019-02-25 (3.27.2)

Fix a bug in the IN operator that was introduced by an attempted optimization in version 3.27.0. Ticket df46dfb631f75694 Fix a bug causing a crash when a window function is misused. Ticket 4feb3159c6bc3f7e33959. Fix various documentation typos Hashes: SQLITE_SOURCE_ID: bd49a8271d650fa89e446b42e513b595a717b9212c91dd384aab871fc1d0f6d7 SHA3-256 for sqlite3.c: 1dbae33bff261f979d0042338f72c9e734b11a80720fb32498bae9150cc576e7

2019-02-08 (3.27.1)

Fix a bug in the query optimizer: an adverse interaction between the OR optimization and the optimization that tries to use values read directly from an expression index instead of recomputing the expression. Ticket 4e8e4857d32d401f Hashes: SQLITE_SOURCE_ID: 2019-02-08 13:17:39 0eca3dd3d38b31c92b49ca2d311128b74584714d9e7de895b1a6286ef959a1dd SHA3-256 for sqlite3.c: 11c14992660d5ac713ea8bea48dc5e6123f26bc8d3075fe5585d1a217d090233

2019-02-07 (3.27.0)

2018-12-01 (3.26.0)

2018-11-05 (3.25.3)

Disallow the use of window functions in the recursive part of a CTE. Ticket e8275b415a2f03bee Fix the behavior of typeof() and length() on virtual tables. Ticket 69d642332d25aa3b7315a6d385 Strengthen defenses against deliberately corrupted database files. Fix a problem in the query planner that results when a row-value expression is used with a PRIMARY KEY with redundant columns. Ticket 1a84668dcfdebaf12415d Fix the query planner so that it works correctly for IS NOT NULL operators in the ON clause of a LEFT JOIN with the SQLITE_ENABLE_STAT4 compile-time option. 65eb38f6e46de8c75e188a17ec Hashes: SQLITE_SOURCE_ID: "2018-11-05 20:37:38 89e099fbe5e13c33e683bef07361231ca525b88f7907be7092058007b75036f2" SHA3-256 for sqlite3.c: 45586e4df74de3a43f3a1f8c7a78c3c3f02edce01af7d10cafe68bb94476a5c5

2018-09-25 (3.25.2)

Add the PRAGMA legacy_alter_table=ON command that causes the "ALTER TABLE RENAME" command to behave as it did in SQLite versions 3.24.0 and earlier: references to the renamed table inside the bodies of triggers and views are not updated. This new pragma provides a compatibility work around for older programs that expected the older, wonky behavior of ALTER TABLE RENAME. Fix a problem with the new window functions implementation that caused a malfunction when complicated expressions involving window functions were used inside of a view. Fixes for various other compiler warnings and minor problems associated with obscure configurations. Hashes: SQLITE_SOURCE_ID: "2018-09-25 19:08:10 fb90e7189ae6d62e77ba3a308ca5d683f90bbe633cf681865365b8e92792d1c7" SHA3-256 for sqlite3.c: 34c23ff91631ae10354f8c9d62fd7d65732b3d7f3acfd0bbae31ff4a62fe28af

2018-09-18 (3.25.1)

Extra sanity checking added to ALTER TABLE in the 3.25.0 release sometimes raises a false-positive when the table being modified has a trigger that updates a virtual table. The false-positive caused the ALTER TABLE to rollback, thus leaving the schema unchanged. Ticket b41031ea2b537237. The fix in the 3.25.0 release for the endless-loop in the byte-code associated with the ORDER BY LIMIT optimization did not work for some queries involving window functions. An additional correction is required. Ticket 510cde277783b5fb Hashes: SQLITE_SOURCE_ID: "2018-09-18 20:20:44 2ac9003de44da7dafa3fbb1915ac5725a9275c86bf2f3b7aa19321bf1460b386" SHA3-256 for sqlite3.c: 1b2302e7a54cc99c84ff699a299f61f069a28e1ed090b89e4430ca80ae2aab06

2018-09-15 (3.25.0)

Add support for window functions Enhancements the ALTER TABLE command: Add support for renaming columns within a table using ALTER TABLE table RENAME COLUMN oldname TO newname. Fix table rename feature so that it also updates references to the renamed table in triggers and views. Query optimizer improvements: Avoid unnecessary loads of columns in an aggregate query that are not within an aggregate function and that are not part of the GROUP BY clause. The IN-early-out optimization: When doing a look-up on a multi-column index and an IN operator is used on a column other than the left-most column, then if no rows match against the first IN value, check to make sure there exist rows that match the columns to the right before continuing with the next IN value. Use the transitive property to try to propagate constant values within the WHERE clause. For example, convert "a=99 AND b=a" into "a=99 AND b=99". Use a separate mutex on every inode in the unix VFS, rather than a single mutex shared among them all, for slightly better concurrency in multi-threaded environments. Enhance the PRAGMA integrity_check command for improved detection of problems on the page freelist. Output infinity as 1e999 in the ".dump" command of the command-line shell. Added the SQLITE_FCNTL_DATA_VERSION file-control. Added the Geopoly module Bug fixes: The ORDER BY LIMIT optimization might have caused an infinite loop in the byte code of the prepared statement under very obscure circumstances, due to a confluence of minor defects in the query optimizer. Fix for ticket 9936b2fa443fec03ff25 On an UPSERT when the order of constraint checks is rearranged, ensure that the affinity transformations on the inserted content occur before any of the constraint checks. Fix for ticket 79cad5e4b2e219dd197242e9e. Avoid using a prepared statement for ".stats on" command of the CLI after it has been closed by the ".eqp full" logicc. Fix for ticket 7be932dfa60a8a6b3b26bcf76. The LIKE optimization was generating incorrect byte-code and hence getting the wrong answer if the left-hand operand has numeric affinity and the right-hand-side pattern is '/%' or if the pattern begins with the ESCAPE character. Fix for ticket c94369cae9b561b1f996d0054b Hashes: SQLITE_SOURCE_ID: "2018-09-15 04:01:47 b63af6c3bd33152742648d5d2e8dc5d5fcbcdd27df409272b6aea00a6f761760" SHA3-256 for sqlite3.c: 989e3ff37f2b5eea8e42205f808ccf0ba86c6ea6aa928ad2c011f33a108ac45d

2018-06-04 (3.24.0)

2018-04-10 (3.23.1)

Fix two problems in the new LEFT JOIN strength reduction optimization. Tickets 1e39b966ae9ee739 and fac496b61722daf2. Fix misbehavior of the FTS5 xBestIndex method. Ticket 2b8aed9f7c9e61e8. Fix a harmless reference to an uninitialized virtual machine register. Ticket 093420fc0eb7cba7. Fix the CLI so that it builds with -DSQLITE_UNTESTABLE Fix the eval.c extension so that it works with PRAGMA empty_result_callbacks=ON. Fix the generate_series virtual table so that it correctly returns no rows if any of its constraints are NULL. Performance enhancements in the parser. Hashes: SQLITE_SOURCE_ID: "2018-04-10 17:39:29 4bb2294022060e61de7da5c227a69ccd846ba330e31626ebcd59a94efd148b3b" SHA3-256 for sqlite3.c: 65750d1e506f416a0b0b9dd22d171379679c733e3460549754dc68c92705b5dc

2018-04-02 (3.23.0)

2018-01-22 (3.22.0)

2017-10-24 (3.21.0)

2017-08-24 (3.20.1)

Fix a potential memory leak in the new sqlite3_result_pointer() interface. Ticket 7486aa54b968e9b5. Hashes: SQLITE_SOURCE_ID: "2017-08-24 16:21:36 8d3a7ea6c5690d6b7c3767558f4f01b511c55463e3f9e64506801fe9b74dce34" SHA3-256 for sqlite3.c: 93b1a6d69b48dc39697d1d3a1e4c30b55da0bdd2cad0c054462f91081832954a

2017-08-01 (3.20.0)

2017-06-17 (3.18.2)

Fix a bug that might cause duplicate output rows when an IN operator is used in the WHERE clause. Ticket 61fe9745. Hashes: SQLITE_SOURCE_ID: "2017-06-17 09:59:36 036ebf729e4b21035d7f4f8e35a6f705e6bf99887889e2dc14ebf2242e7930dd" SHA3-256 for sqlite3.c: b0bd014f2776b9f9508a3fc6432f70e2436bf54475369f88f0aeef75b0eec93e

2017-06-16 (3.18.1)

Fix a bug associated with auto_vacuum that can lead to database corruption. The bug was introduced in version 3.16.0 (2017-01-02). Ticket fda22108. Hashes: SQLITE_SOURCE_ID: "2017-06-16 13:41:15 77bb46233db03a3338bacf7e56f439be3dfd1926ea0c44d252eeafa7a7b31c06" SHA3-256 for sqlite3.c: 334eaf776db9d09a4e69d6012c266bc837107edc2c981739ef82081cb11c5723

2017-06-08 (3.19.3)

Fix a bug associated with auto_vacuum that can lead to database corruption. The bug was introduced in version 3.16.0 (2017-01-02). Ticket fda22108. Hashes: SQLITE_SOURCE_ID: "2017-06-08 14:26:16 0ee482a1e0eae22e08edc8978c9733a96603d4509645f348ebf55b579e89636b" SHA3-256 for sqlite3.c: 368f1d31272b1739f804bcfa5485e5de62678015c4adbe575003ded85c164bb8

2017-05-25 (3.19.2)

Fix more bugs in the LEFT JOIN flattening optimization. Ticket 7fde638e94287d2c. Hashes: SQLITE_SOURCE_ID: "2017-05-25 16:50:27 edb4e819b0c058c7d74d27ebd14cc5ceb2bad6a6144a486a970182b7afe3f8b9" SHA3-256 for sqlite3.c: 1be0c457869c1f7eba58c3b5097b9ec307a15be338308bee8e5be8570bcf5d1e

2017-05-24 (3.19.1)

Fix a bug in the LEFT JOIN flattening optimization. Ticket cad1ab4cb7b0fc. Remove a surplus semicolon that was causing problems for older versions of MSVC. Hashes: SQLITE_SOURCE_ID: "2017-05-24 13:08:33 f6d7b988f40217821a382bc298180e9e6794f3ed79a83c6ef5cae048989b3f86" SHA3-256 for sqlite3.c: 996b2aff37b6e0c6663d0312cd921bbdf6826c989cbbb07dadde5e9672889bca

2017-05-22 (3.19.0)

The SQLITE_READ authorizer callback is invoked once with a column name that is an empty string for every table referenced in a query from which no columns are extracted. When using an index on an expression, try to use expression values already available in the index, rather than loading the original columns and recomputing the expression. Enhance the flattening optimization so that it is able to flatten views on the right-hand side of a LEFT JOIN. Use replace() instead of char() for escaping newline and carriage-return characters embedded in strings in the .dump output from the command-line shell. Avoid unnecessary foreign key processing in UPDATE statements that do not touch the columns that are constrained by the foreign keys. On a DISTINCT query that uses an index, try to skip ahead to the next distinct entry using the index rather than stepping through rows, when an appropriate index is available. Avoid unnecessary invalidation of sqlite3_blob handles when making changes to unrelated tables. Transfer any terms of the HAVING clause that use only columns mentioned in the GROUP BY clause over to the WHERE clause for faster processing. Reuse the same materialization of a VIEW if that VIEW appears more than once in the same query. Enhance PRAGMA integrity_check so that it identifies tables that have two or more rows with the same rowid. Enhance the FTS5 query syntax so that column filters may be applied to arbitrary expressions. Enhance the json_extract() function to cache and reuse parses of JSON input text. Added the anycollseq.c loadable extension that allows a generic SQLite database connection to read a schema that contains unknown and/or application-specific collating sequences. Bug Fixes: Fix a problem in REPLACE that can result in a corrupt database containing two or more rows with the same rowid. Fix for ticket f68dc596c4e6018d. Fix a problem in PRAGMA integrity_check that was causing a subsequent VACUUM to behave suboptimally. Fix the PRAGMA foreign_key_check command so that it works correctly with foreign keys on WITHOUT ROWID tables. Fix a bug in the b-tree logic that can result in incorrect duplicate answers for IN operator queries. Ticket 61fe9745 Disallow leading zeros in numeric constants in JSON. Fix for ticket b93be8729a895a528e2. Disallow control characters inside of strings in JSON. Fix for ticket 6c9b5514077fed34551. Limit the depth of recursion for JSON objects and arrays in order to avoid excess stack usage in the recursive descent parser. Fix for ticket 981329adeef51011052. Hashes: SQLITE_SOURCE_ID: "2017-05-22 13:58:13 28a94eb282822cad1d1420f2dad6bf65e4b8b9062eda4a0b9ee8270b2c608e40" SHA3-256 for sqlite3.c: c30326aa1a9cc342061b755725eac9270109acf878bc59200dd4b1cea6bc2908

2017-03-30 (3.18.0)

2017-02-13 (3.17.0)

Approximately 25% better performance from the R-Tree extension. Uses compiler built-ins (ex: __builtin_bswap32() or _byteswap_ulong()) for byteswapping when available. Uses the sqlite3_blob key/value access object instead of SQL for pulling content out of R-Tree nodes Other miscellaneous enhancements such as loop unrolling. Add the SQLITE_DEFAULT_LOOKASIDE compile-time option. Increase the default lookaside size from 512,125 to 1200,100 as this provides better performance while only adding 56KB of extra memory per connection. Memory-sensitive applications can restore the old default at compile-time, start-time, or run-time. Use compiler built-ins __builtin_sub_overflow(), __builtin_add_overflow(), and __builtin_mul_overflow() when available. (All compiler built-ins can be omitted with the SQLITE_DISABLE_INTRINSIC compile-time option.) Added the SQLITE_ENABLE_NULL_TRIM compile-time option, which can result in significantly smaller database files for some applications, at the risk of being incompatible with older versions of SQLite. Change SQLITE_DEFAULT_PCACHE_INITSZ from 100 to 20, for improved performance. Added the SQLITE_UINT64_TYPE compile-time option as an analog to SQLITE_INT64_TYPE. Perform some UPDATE operations in a single pass instead of in two passes. Enhance the session extension to support WITHOUT ROWID tables. Fixed performance problems and potential stack overflows when creating views from multi-row VALUES clauses with hundreds of thousands of rows. Added the sha1.c extension. In the command-line shell, enhance the ".mode" command so that it restores the default column and row separators for modes "line", "list", "column", and "tcl". Enhance the SQLITE_DIRECT_OVERFLOW_READ option so that it works in WAL mode as long as the pages being read are not in the WAL file. Enhance the Lemon parser generator so that it can store the parser object as a stack variable rather than allocating space from the heap and make use of that enhancement in the amalgamation. Other performance improvements. Uses about 6.5% fewer CPU cycles. Bug Fixes: Throw an error if the ON clause of a LEFT JOIN references tables to the right of the ON clause. This is the same behavior as PostgreSQL. Formerly, SQLite silently converted the LEFT JOIN into an INNER JOIN. Fix for ticket 25e335f802dd. Use the correct affinity for columns of automatic indexes. Ticket 7ffd1ca1d2ad4ec. Ensure that the sqlite3_blob_reopen() interface can correctly handle short rows. Fix for ticket e6e962d6b0f06f46e. Hashes: SQLITE_SOURCE_ID: "2017-02-13 16:02:40 ada05cfa86ad7f5645450ac7a2a21c9aa6e57d2c" SHA1 for sqlite3.c: cc7d708bb073c44102a59ed63ce6142da1f174d1

2017-01-06 (3.16.2)

Fix the REPLACE statement for WITHOUT ROWID tables that lack secondary indexes so that it works correctly with triggers and foreign keys. This was a new bug caused by performance optimizations added in version 3.16.0. Ticket 30027b613b4 Fix the sqlite3_value_text() interface so that it correctly translates content generated by zeroblob() into a string of all 0x00 characters. This is a long-standing issue discovered after the 3.16.1 release by OSS-Fuzz Fix the bytecode generator to deal with a subquery in the FROM clause that is itself a UNION ALL where one side of the UNION ALL is a view that contains an ORDER BY. This is a long-standing issue that was discovered after the release of 3.16.1. See ticket 190c2507. Adjust the sqlite3_column_count() API so it more often returns the same values for PRAGMA statements as it did in prior releases, to minimize disruption to applications that might be using that interface in unexpected ways. Hashes: SQLITE_SOURCE_ID: "2017-01-06 16:32:41 a65a62893ca8319e89e48b8a38cf8a59c69a8209" SHA1 for sqlite3.c: 2bebdc3f24911c0d12b6d6c0123c3f84d6946b08

2017-01-03 (3.16.1)

Fix a bug concerning the use of row values within triggers (see ticket 8c9458e7) that was in version 3.15.0 but was not reported until moments after the 3.16.0 release was published. Hashes: SQLITE_SOURCE_ID: "2017-01-03 18:27:03 979f04392853b8053817a3eea2fc679947b437fd" SHA1 for sqlite3.c: 354f6223490b30fd5320b4066b1535e4ce33988d

2017-01-02 (3.16.0)

2016-11-28 (3.15.2)

Multiple bug fixes to the row value logic that was introduced in version 3.15.0. Fix a NULL pointer dereference in ATTACH/DETACH following a maliciously constructed syntax error. Ticket 2f1b168ab4d4844. Fix a crash that can occur following an out-of-memory condition in the built-in instr() function. In the JSON extension, fix the JSON validator so that it correctly rejects invalid backslash escapes within strings. Hashes: SQLITE_SOURCE_ID: "2016-11-28 19:13:37 bbd85d235f7037c6a033a9690534391ffeacecc8" SHA1 for sqlite3.c: 06d77b42a3e70609f8d4bbb97caf53652f1082cb

2016-11-04 (3.15.1)

Added SQLITE_FCNTL_WIN32_GET_HANDLE file control opcode. Fix the VACUUM command so that it spills excess content to disk rather than holding everything in memory, and possible causing an out-of-memory error for larger database files. This fixes an issue introduced by version 3.15.0. Fix a case (present since 3.8.0 - 2013-08-26) where OR-connected terms in the ON clause of a LEFT JOIN might cause incorrect results. Ticket 34a579141b2c5ac. Fix a case where the use of row values in the ON clause of a LEFT JOIN might cause incorrect results. Ticket fef4bb4bd9185ec8f. Hashes: SQLITE_SOURCE_ID: "2016-11-04 12:08:49 1136863c76576110e710dd5d69ab6bf347c65e36" SHA1 for sqlite3.c: e7c26a7be3e431dd06898f8d262c4ef240c07366

2016-10-14 (3.15.0)

2016-09-12 (3.14.2)

Improved support for using the STDCALL calling convention in winsqlite3.dll. Fix the sqlite3_trace_v2() interface so that it is disabled if either the callback or the mask arguments are zero, in accordance with the documentation. Fix commenting errors and improve the comments generated on EXPLAIN listings when the -DSQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option is used. Fix the ".read" command in the command-line shell so that it understands that its input is not interactive. Correct affinity computations for a SELECT on the RHS of an IN operator. Fix for ticket 199df4168c. The ORDER BY LIMIT optimization is not valid unless the inner-most IN operator loop is actually used by the query plan. Fix for ticket 0c4df46116e90f92. Fix an internal code generator problem that was causing some DELETE operations to no-op. Ticket ef360601 Hashes: SQLITE_SOURCE_ID: "2016-09-12 18:50:49 29dbef4b8585f753861a36d6dd102ca634197bd6" SHA1 for sqlite3.c: bcc4a1989db45e7f223191f2d0f66c1c28946383

2016-08-11 (3.14.1)

A performance enhancement to the page-cache "truncate" operation reduces COMMIT time by dozens of milliseconds on systems with a large page cache. Fix to the --rbu option of sqldiff. Hashes: SQLITE_SOURCE_ID: "2016-08-11 18:53:32 a12d8059770df4bca59e321c266410344242bf7b" SHA1 for sqlite3.c: d545b24892278272ce4e40e0567d69c8babf12ea

2016-08-08 (3.14)

2016-05-18 (3.13.0)

2016-04-18 (3.12.2)

Fix a backwards compatibility problem in version 3.12.0 and 3.12.1: Columns declared as "INTEGER" PRIMARY KEY (with quotes around the datatype keyword) were not being recognized as an INTEGER PRIMARY KEY, which resulted in an incompatible database file. Ticket 7d7525cb01b68 Fix a bug (present since version 3.9.0) that can cause the DELETE operation to miss rows if PRAGMA reverse_unordered_selects is turned on. Ticket a306e56ff68b8fa5 Fix a bug in the code generator that can cause incorrect results if two or more virtual tables are joined and the virtual table used in outer loop of the join has an IN operator constraint. Correctly interpret negative "PRAGMA cache_size" values when determining the cache size used for sorting large amounts of data. Hashes: SQLITE_SOURCE_ID: "2016-04-18 17:30:31 92dc59fd5ad66f646666042eb04195e3a61a9e8e" SHA1 for sqlite3.c: de5a5898ebd3a3477d4652db143746d008b24c83

2016-04-08 (3.12.1)

Fix a boundary condition error introduced by version 3.12.0 that can result in a crash during heavy SAVEPOINT usage. Ticket 7f7f8026eda38. Fix views so that they inherit column datatypes from the table that they are defined against, when possible. Fix the query planner so that IS and IS NULL operators are able to drive an index on a LEFT OUTER JOIN. Hashes: SQLITE_SOURCE_ID: "2016-04-08 15:09:49 fe7d3b75fe1bde41511b323925af8ae1b910bc4d" SHA1 for sqlite3.c: ebb18593350779850e3e1a930eb84a70fca8c1d1

2016-04-01 (3.9.3)

Backport a simple query planner optimization that allows the IS operator to drive an index on a LEFT OUTER JOIN. No other changes from the version 3.9.2 baseline.

2016-03-29 (3.12.0)

2016-03-03 (3.11.1)

Improvements to the Makefiles and build scripts used by VisualStudio. Fix an FTS5 issue in which the 'optimize' command could cause index corruption. Fix a buffer overread that might occur if FTS5 is used to query a corrupt database file. Increase the maximum "scope" value for the spellfix1 extension from 6 to 30. SQLITE_SOURCE_ID: "2016-03-03 16:17:53 f047920ce16971e573bc6ec9a48b118c9de2b3a7" SHA1 for sqlite3.c: 3da832fd2af36eaedb05d61a8f4c2bb9f3d54265

2016-02-15 (3.11.0)

2016-01-20 (3.10.2)

Critical bug fix: Version 3.10.0 introduced a case-folding bug in the LIKE operator which is fixed by this patch release. Ticket 80369eddd5c94. Other miscellaneous bug fixes: Fix a use-after-free that can occur when SQLite is compiled with -DSQLITE_HAS_CODEC. Fix the build so that it works with -DSQLITE_OMIT_WAL. Fix the configure script for the amalgamation so that the --readline option works again on Raspberry PIs. Hashes: SQLITE_SOURCE_ID: "2016-01-20 15:27:19 17efb4209f97fb4971656086b138599a91a75ff9" SHA1 for sqlite3.c: f7088b19d97cd7a1c805ee95c696abd54f01de4f

2016-01-14 (3.10.1)

New feature: Add the SQLITE_FCNTL_JOURNAL_POINTER file control. Bug fix: Fix a 16-month-old bug in the query planner that could generate incorrect results when a scalar subquery attempts to use the block sorting optimization. Ticket cb3aa0641d9a4. Hashes: SQLITE_SOURCE_ID: "2016-01-13 21:41:56 254419c36766225ca542ae873ed38255e3fb8588" SHA1 for sqlite3.c: 1398ba8e4043550a533cdd0834bfdad1c9eab0f4

2016-01-06 (3.10.0)

2015-11-02 (3.9.2)

Fix the schema parser so that it interprets certain (obscure and ill-formed) CREATE TABLE statements the same as legacy. Fix for ticket ac661962a2aeab3c331 Fix a query planner problem that could result in an incorrect answer due to the use of automatic indexing in subqueries in the FROM clause of a correlated scalar subqueries. Fix for ticket 8a2adec1. SQLITE_SOURCE_ID: "2015-11-02 18:31:45 bda77dda9697c463c3d0704014d51627fceee328" SHA1 for sqlite3.c: 1c4013876f50bbaa3e6f0f98e0147c76287684c1

2015-10-16 (3.9.1)

Fix the json1 extension so that it does not recognize ASCII form-feed as a whitespace character, in order to comply with RFC-7159. Fix for ticket 57eec374ae1d0a1d Add a few #ifdef and build script changes to address compilation issues that appeared after the 3.9.0 release. SQLITE_SOURCE_ID: ""2015-10-16 17:31:12 767c1727fec4ce11b83f25b3f1bfcfe68a2c8b02" SHA1 for sqlite3.c: 5e6d1873a32d82c2cf8581f143649940cac8ae49

2015-10-14 (3.9.0)

2015-07-29 (3.8.11.1)

Restore an undocumented side-effect of PRAGMA cache_size: force the database schema to be parsed if the database has not been previously accessed. Fix a long-standing problem in sqlite3_changes() for WITHOUT ROWID tables that was reported a few hours after the 3.8.11 release. SQLITE_SOURCE_ID: "2015-07-29 20:00:57 cf538e2783e468bbc25e7cb2a9ee64d3e0e80b2f" SHA1 for sqlite3.c: 3be71d99121fe5b17f057011025bcf84e7cc6c84

2015-07-27 (3.8.11)

2015-05-20 (3.8.10.2)

Fix an index corruption issue introduced by version 3.8.7. An index with a TEXT key can be corrupted by an INSERT into the corresponding table if the table has two nested triggers that convert the key value to INTEGER and back to TEXT again. Ticket 34cd55d68e0 SQLITE_SOURCE_ID: "2015-05-20 18:17:19 2ef4f3a5b1d1d0c4338f8243d40a2452cc1f7fe4" SHA1 for sqlite3.c: 638abb77965332c956dbbd2c8e4248e84da4eb63

2015-05-09 (3.8.10.1)

Make sqlite3_compileoption_used() responsive to the SQLITE_ENABLE_DBSTAT_VTAB compile-time option. Fix a harmless warning in the command-line shell on some versions of MSVC. Fix minor issues with the dbstat virtual table. SQLITE_SOURCE_ID: "2015-05-09 12:14:55 05b4b1f2a937c06c90db70c09890038f6c98ec40" SHA1 for sqlite3.c: 85e4e1c08c7df28ef61bb9759a0d466e0eefbaa2

2015-05-07 (3.8.10)

2015-04-08 (3.8.9)

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. Fix a bug in the fts3 snippet() function causing it to omit leading separator characters from snippets that begin with the first token in a column. SQLITE_SOURCE_ID: "2015-04-08 12:16:33 8a8ffc862e96f57aa698f93de10dee28e69f6e09" SHA1 for sqlite3.c: 49f1c3ae347e1327b5aaa6c7f76126bdf09c6f42

2015-02-25 (3.8.8.3)

Fix a bug (ticket 2326c258d02ead33) that can lead to incorrect results if the qualifying constraint of a partial index appears in the ON clause of a LEFT JOIN. Added the ability to link against the "linenoise" command-line editing library in unix builds of the command-line shell. SQLITE_SOURCE_ID: "2015-02-25 13:29:11 9d6c1880fb75660bbabd693175579529785f8a6b" SHA1 for sqlite3.c: 74ee38c8c6fd175ec85a47276dfcefe8a262827a

2015-01-30 (3.8.8.2)

Enhance sqlite3_wal_checkpoint_v2(TRUNCATE) interface so that it truncates the WAL file even if there is no checkpoint work to be done. SQLITE_SOURCE_ID: "2015-01-30 14:30:45 7757fc721220e136620a89c9d28247f28bbbc098" SHA1 for sqlite3.c: 85ce79948116aa9a087ec345c9d2ce2c1d3cd8af

2015-01-20 (3.8.8.1)

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. Ticket f97c4637102a3ae72b79. SQLITE_SOURCE_ID: "2015-01-20 16:51:25 f73337e3e289915a76ca96e7a05a1a8d4e890d55" SHA1 for sqlite3.c: 33987fb50dcc09f1429a653d6b47672f5a96f19e

2015-01-16 (3.8.8)

2014-12-09 (3.8.7.4)

Bug fix: Add in a mutex that was omitted from the previous release. SQLITE_SOURCE_ID: "2014-12-09 01:34:36 f66f7a17b78ba617acde90fc810107f34f1a1f2e" SHA1 for sqlite3.c: 0a56693a3c24aa3217098afab1b6fecccdedfd23

2014-12-05 (3.8.7.3)

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. Bug fix: Recognize that any column in the right-hand table of a LEFT JOIN can be NULL even if the column has a NOT NULL constraint. Do not apply optimizations that assume the column is never NULL. Ticket 6f2222d550f5b0ee7ed. SQLITE_SOURCE_ID: "2014-12-05 22:29:24 647e77e853e81a5effeb4c33477910400a67ba86" SHA1 for sqlite3.c: 3ad2f5ba3a4a3e3e51a1dac9fda9224b359f0261

2014-11-18 (3.8.7.2)

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. Ticket 094d39a4c95ee4. 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. Ticket db87229497. SQLITE_SOURCE_ID: "2014-11-18 20:57:56 2ab564bf9655b7c7b97ab85cafc8a48329b27f93" SHA1 for sqlite3.c: b2a68d5783f48dba6a8cb50d8bf69b238c5ec53a

2014-10-29 (3.8.7.1)

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. Fix a couple of problems associated with running an UPDATE or DELETE on a VIEW with a rowid in the WHERE clause. SQLITE_SOURCE_ID: "2014-10-29 13:59:56 3b7b72c4685aa5cf5e675c2c47ebec10d9704221" SHA1 for sqlite3.c: 2d25bd1a73dc40f538f3a81c28e6efa5999bdf0c

2014-10-17 (3.8.7)

Performance Enhancements: 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. Ticket 98d973b8f5. 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. Ticket ba7cbfaedc7e6. 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. Ticket 11d5aa455e0d98f3c1e6a08 Fix a faulty assert() statement. Ticket 369d57fb8e5ccdff06f1 Test, Debug, and Analysis Changes: Show ASCII-art abstract syntax tree diagrams using the ".selecttrace" and ".wheretrace" commands in the command-line shell when compiled with SQLITE_DEBUG, SQLITE_ENABLE_SELECTTRACE, and SQLITE_ENABLE_WHERETRACE. Also provide the sqlite3TreeViewExpr() and sqlite3TreeViewSelect() entry points that can be invoked from with the debugger to show the parse tree when stopped at a breakpoint. Drop support for SQLITE_ENABLE_TREE_EXPLAIN. The SELECTTRACE mechanism provides more useful diagnostics information. New options to the command-line shell for configuring auxiliary memory usage: --pagecache, --lookaside, and --scratch. SQLITE_SOURCE_ID: "2014-10-17 11:24:17 e4ab094f8afce0817f4074e823fabe59fc29ebb4" SHA1 for sqlite3.c: 56dcf5e931a9e1fa12fc2d600cd91d3bf9b639cd

2014-08-15 (3.8.6)

2014-06-04 (3.8.5)

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. Ticket 07d6a0453d Assertion fault on queries involving expressions of the form "x IN (?)". Ticket e39d032577. Incorrect column datatype reported. Ticket a8a0d2996a 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. Ticket 10fb063b11 Partial index causes assertion fault on UPDATE OR REPLACE. Ticket 2ea3e9fe63 Crash when calling undocumented SQL function sqlite_rename_parent() with NULL parameters. Ticket 264b970c43 ORDER BY ignored if the query has an identical GROUP BY. Ticket b75a9ca6b0 The group_concat(x,'') SQL function returns NULL instead of an empty string when all inputs are empty strings. Ticket 55746f9e65 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. Ticket e9654505cfd Fix a problem in CSV import in the command-line shell where if the leftmost field of the first row in the CSV file was both zero bytes in size and unquoted no data would be imported. Fix a problem in FTS4 where the left-most column that contained the notindexed column name as a prefix was not indexed rather than the column whose name matched exactly. Fix the sqlite3_db_readonly() interface so that it returns true if the database is read-only due to the file format write version number being too large. SQLITE_SOURCE_ID: "2014-06-04 14:06:34 b1ed4f2a34ba66c29b130f8d13e9092758019212" SHA1 for sqlite3.c: 7bc194957238c61b1a47f301270286be5bc5208c

2014-04-03 (3.8.4.3)

Add a one-character fix for a problem that might cause incorrect query results on a query that mixes DISTINCT, GROUP BY in a subquery, and ORDER BY. Ticket 98825a79ce14. SQLITE_SOURCE_ID: "2014-04-03 16:53:12 a611fa96c4a848614efe899130359c9f6fb889c3" SHA1 for sqlite3.c: 310a1faeb9332a3cd8d1f53b4a2e055abf537bdc

2014-03-26 (3.8.4.2)

Fix a potential buffer overread that could result when trying to search a corrupt database file. SQLITE_SOURCE_ID: "2014-03-26 18:51:19 02ea166372bdb2ef9d8dfbb05e78a97609673a8e" SHA1 for sqlite3.c: 4685ca86c2ea0649ed9f59a500013e90b3fe6d03

2014-03-11 (3.8.4.1)

Work around a C-preprocessor macro conflict that breaks the build for some configurations with Microsoft Visual Studio. When computing the cost of the skip-scan optimization, take into account the fact that multiple seeks are required. SQLITE_SOURCE_ID: "2014-03-11 15:27:36 018d317b1257ce68a92908b05c9c7cf1494050d0" SHA1 for sqlite3.c: d5cd1535053a50aa8633725e3595740b33709ac5

2014-03-10 (3.8.4)

Code optimization and refactoring for improved performance. Add the ".clone" and ".save" commands to the command-line shell. Update the banner on the command-line shell to alert novice users when they are using an ephemeral in-memory database. Fix editline support in the command-line shell. Add support for coverage testing of VDBE programs using the SQLITE_TESTCTRL_VDBE_COVERAGE verb of sqlite3_test_control(). Update the _FILE_OFFSET_BITS macro so that builds work again on QNX. Change the datatype of SrcList.nSrc from type u8 to type int to work around an issue in the C compiler on AIX. Get extension loading working on Cygwin. Bug fix: Fix the char() SQL function so that it returns an empty string rather than an "out of memory" error when called with zero arguments. Bug fix: DISTINCT now recognizes that a zeroblob and a blob of all 0x00 bytes are the same thing. Ticket [fccbde530a] Bug fix: Compute the correct answer for queries that contain an IS NOT NULL term in the WHERE clause and also contain an OR term in the WHERE clause and are compiled with SQLITE_ENABLE_STAT4. Ticket [4c86b126f2] Bug fix: Make sure "rowid" columns are correctly resolved in joins between normal tables and WITHOUT ROWID tables. Ticket [c34d0557f7] Bug fix: Make sure the same temporary registers are not used in concurrent co-routines used to implement compound SELECT statements containing ORDER BY clauses, as such use can lead to incorrect answers. Ticket [8c63ff0eca] Bug fix: Ensure that "ORDER BY random()" clauses do not get optimized out. Ticket [65bdeb9739] Bug fix: Repair a name-resolution error that can occur in sub-select statements contained within a TRIGGER. Ticket [4ef7e3cfca] Bug fix: Fix column default values expressions of the form "DEFAULT(-(-9223372036854775808))" so that they work correctly, initializing the column to a floating point value approximately equal to +9223372036854775808.0. SQLITE_SOURCE_ID: "2014-03-10 12:20:37 530a1ee7dc2435f80960ce4710a3c2d2bfaaccc5" SHA1 for sqlite3.c: b0c22e5f15f5ba2afd017ecd990ea507918afe1c

2014-02-11 (3.8.3.1)

Fix a bug (ticket 4c86b126f2) that causes rows to go missing on some queries with OR clauses and IS NOT NULL operators in the WHERE clause, when the SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4 compile-time options are used. Fix a harmless compiler warning that was causing problems for VS2013. SQLITE_SOURCE_ID: "2014-02-11 14:52:19 ea3317a4803d71d88183b29f1d3086f46d68a00e" SHA1 for sqlite3.c: 990004ef2d0eec6a339e4caa562423897fe02bf0

2014-02-03 (3.8.3)

Added support for common table expressions and the WITH clause. Added the printf() SQL function. Added SQLITE_DETERMINISTIC as an optional bit in the 4th argument to the sqlite3_create_function() and related interfaces, providing applications with the ability to create new functions that can be factored out of inner loops when they have constant arguments. Add SQLITE_READONLY_DBMOVED error code, returned at the beginning of a transaction, to indicate that the underlying database file has been renamed or moved out from under SQLite. Allow arbitrary expressions, including function calls and subqueries, in the filename argument to ATTACH. Allow a VALUES clause to be used anywhere a SELECT statement is valid. Reseed the PRNG used by sqlite3_randomness(N,P) when invoked with N==0. Automatically reseed after a fork() on unix. Enhance the spellfix1 virtual table so that it can search efficiently by rowid. Performance enhancements. Improvements to the comments in the VDBE byte-code display when running EXPLAIN. Add the "%token_class" directive to Lemon parser generator and use it to simplify the grammar. Change the Lemon source code to avoid calling C-library functions that OpenBSD considers dangerous. (Ex: sprintf). Bug fix: In the command-line shell CSV import feature, do not end a field when an escaped double-quote occurs at the end of a CRLN line. SQLITE_SOURCE_ID: "2014-02-03 13:52:03 e816dd924619db5f766de6df74ea2194f3e3b538" SHA1 for sqlite3.c: 98a07da78f71b0275e8d9c510486877adc31dbee

2013-12-06 (3.8.2)

Changed the defined behavior for the CAST expression when floating point values greater than +9223372036854775807 are cast into into integers so that the result is the largest possible integer, +9223372036854775807, instead of the smallest possible integer, -9223372036854775808. After this change, CAST(9223372036854775809.0 as INT) yields +9223372036854775807 instead of -9223372036854775808. ← Potentially Incompatible Change! Added support for WITHOUT ROWID tables. Added the skip-scan optimization to the query planner. Extended the virtual table interface, and in particular the sqlite3_index_info object to allow a virtual table to report its estimate on the number of rows that will be returned by a query. Update the R-Tree extension to make use of the enhanced virtual table interface. Add the SQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option. Enhanced the comments that are inserted into EXPLAIN output when the SQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option is enabled. Performance enhancements in the VDBE, especially to the OP_Column opcode. Factor constant subexpressions in inner loops out to the initialization code in prepared statements. Enhanced the ".explain" output formatting of the command-line shell so that loops are indented to better show the structure of the program. Enhanced the ".timer" feature of the command-line shell so that it shows wall-clock time in addition to system and user times. SQLITE_SOURCE_ID: "2013-12-06 14:53:30 27392118af4c38c5203a04b8013e1afdb1cebd0d" SHA1 for sqlite3.c: 6422c7d69866f5ea3db0968f67ee596e7114544e

2013-10-17 (3.8.1)

Added the unlikely() and likelihood() SQL functions to be used as hints to the query planner. Enhancements to the query planner: Take into account the fact WHERE clause terms that cannot be used with indices still probably reduce the number of output rows. Estimate the sizes of table and index rows and use the smallest applicable B-Tree for full scans and "count(*)" operations. Added the soft_heap_limit pragma. Added support for SQLITE_ENABLE_STAT4 Added support for "sz=NNN" parameters at the end of sqlite_stat1.stat fields used to specify the average length in bytes for table and index rows. Avoid running foreign-key constraint checks on an UPDATE if none of the modified columns are associated with foreign keys. Added the SQLITE_MINIMUM_FILE_DESCRIPTOR compile-time option Added the win32-longpath VFS on windows, permitting filenames up to 32K characters in length. The Date And Time Functions are enhanced so that the current time (ex: julianday('now')) is always the same for multiple function invocations within the same sqlite3_step() call. Add the "totype.c" extension, implementing the tointeger() and toreal() SQL functions. FTS4 queries are better able to make use of docidAdded the hidden fts4aux languageid column to the fts4aux virtual table. The VACUUM command packs the database about 1% tighter. The sqlite3_analyzer utility program is updated to provide better descriptions and to compute a more accurate estimate for "Non-sequential pages" Refactor the implementation of PRAGMA statements to improve parsing performance. The directory used to hold temporary files on unix can now be set using the SQLITE_TMPDIR environment variable, which takes precedence over the TMPDIR environment variable. The sqlite3_temp_directory global variable still has higher precedence than both environment variables, however. Added the PRAGMA stats statement. Bug fix: Return the correct answer for "SELECT count(*) FROM table" even if there is a partial index on the table. Ticket a5c8ed66ca. SQLITE_SOURCE_ID: "2013-10-17 12:57:35 c78be6d786c19073b3a6730dfe3fb1be54f5657a" SHA1 for sqlite3.c: 0a54d76566728c2ba96292a49b138e4f69a7c391

2013-09-03 (3.8.0.2)

Fix a bug in the optimization that attempts to omit unused LEFT JOINs SQLITE_SOURCE_ID: "2013-09-03 17:11:13 7dd4968f235d6e1ca9547cda9cf3bd570e1609ef" SHA1 for sqlite3.c: 6cf0c7b46975a87a0dc3fba69c229a7de61b0c21

2013-08-29 (3.8.0.1)

Fix an off-by-one error that caused quoted empty string at the end of a CRNL-terminated line of CSV input to be misread by the command-line shell. Fix a query planner bug involving a LEFT JOIN with a BETWEEN or LIKE/GLOB constraint and then another INNER JOIN to the right that involves an OR constraint. Fix a query planner bug that could result in a segfault when querying tables with a UNIQUE or PRIMARY KEY constraint with more than four columns. SQLITE_SOURCE_ID: "2013-08-29 17:35:01 352362bc01660edfbda08179d60f09e2038a2f49" SHA1 for sqlite3.c: 99906bf63e6cef63d6f3d7f8526ac4a70e76559e

2013-08-26 (3.8.0)

2013-05-20 (3.7.17)

2013-04-12 (3.7.16.2)

Fix a bug (present since version 3.7.13) that could result in database corruption on windows if two or more processes try to access the same database file at the same time and immediately after third process crashed in the middle of committing to that same file. See ticket 7ff3120e4f for further information. SQLITE_SOURCE_ID: "2013-04-12 11:52:43 cbea02d93865ce0e06789db95fd9168ebac970c7" SHA1 for sqlite3.c: d466b54789dff4fb0238b9232e74896deaefab94

2013-03-29 (3.7.16.1)

Fix for a bug in the ORDER BY optimizer that was introduced in version 3.7.15 which would sometimes optimize out the sorting step when in fact the sort was required. Ticket a179fe7465 Fix a long-standing bug in the CAST expression that would recognize UTF16 characters as digits even if their most-significant-byte was not zero. Ticket 689137afb6da41. Fix a bug in the NEAR operator of FTS3 when applied to subfields. Ticket 38b1ae018f. Fix a long-standing bug in the storage engine that would (very rarely) cause a spurious report of an SQLITE_CORRUPT error but which was otherwise harmless. Ticket 6bfb98dfc0c. The SQLITE_OMIT_MERGE_SORT option has been removed. The merge sorter is now a required component of SQLite. Fixed lots of spelling errors in the source-code comments SQLITE_SOURCE_ID: "2013-03-29 13:44:34 527231bc67285f01fb18d4451b28f61da3c4e39d" SHA1 for sqlite3.c: 7a91ceceac9bcf47ceb8219126276e5518f7ff5a

2013-03-18 (3.7.16)

Added the PRAGMA foreign_key_check command. Added new extended error codes for all SQLITE_CONSTRAINT errors Added the SQLITE_READONLY_ROLLBACK extended error code for when a database cannot be opened because it needs rollback recovery but is read-only. Added SQL functions unicode(A) and char(X1,...,XN). Performance improvements for PRAGMA incremental_vacuum, especially in cases where the number of free pages is greater than what will fit on a single trunk page of the freelist. Improved optimization of queries containing aggregate min() or max(). Enhance virtual tables so that they can potentially use an index when the WHERE clause contains the IN operator. Allow indices to be used for sorting even if prior terms of the index are constrained by IN operators in the WHERE clause. Enhance the PRAGMA table_info command so that the "pk" column is an increasing integer to show the order of columns in the primary key. Enhance the query optimizer to exploit transitive join constraints. Performance improvements in the query optimizer. Allow the error message from PRAGMA integrity_check to be longer than 20000 bytes. Improved name resolution for deeply nested queries. Added the test_regexp.c module as a demonstration of how to implement the REGEXP operator. Improved error messages in the RTREE extension. Enhance the command-line shell so that a non-zero argument to the ".exit" command causes the shell to exit immediately without cleanly shutting down the database connection. Improved error messages for invalid boolean arguments to dot-commands in the command-line shell. Improved error messages for "foreign key mismatch" showing the names of the two tables involved. Remove all uses of umask() in the unix VFS. Added the PRAGMA vdbe_addoptrace and PRAGMA vdbe_debug commands. Change to use strncmp() or the equivalent instead of memcmp() when comparing non-zero-terminated strings. Update cygwin interfaces to omit deprecated API calls. Enhance the spellfix1 extension so that the edit distance cost table can be changed at runtime by inserting a string like 'edit_cost_table=TABLE' into the "command" field. Bug fix: repair a long-standing problem that could cause incorrect query results in a 3-way or larger join that compared INTEGER fields against TEXT fields in two or more places. Ticket fc7bd6358f Bug fix: Issue an error message if the 16-bit reference counter on a view overflows due to an overly complex query. Bug fix: Avoid leaking memory on LIMIT and OFFSET clauses in deeply nested UNION ALL queries. Bug fix: Make sure the schema is up-to-date prior to running pragmas table_info, index_list, index_info, and foreign_key_list. SQLITE_SOURCE_ID: "2013-03-18 11:39:23 66d5f2b76750f3520eb7a495f6247206758f5b90" SHA1 for sqlite3.c: 7308ab891ca1b2ebc596025cfe4dc36f1ee89cf6

2013-01-09 (3.7.15.2)

Fix a bug, introduced in version 3.7.15, that causes an ORDER BY clause to be optimized out of a three-way join when the ORDER BY is actually required. Ticket 598f5f7596b055 SQLITE_SOURCE_ID: "2013-01-09 11:53:05 c0e09560d26f0a6456be9dd3447f5311eb4f238f" SHA1 for sqlite3.c: 5741f47d1bc38aa0a8c38f09e60a5fe0031f272d

2012-12-19 (3.7.15.1)

Fix a bug, introduced in version 3.7.15, that causes a segfault if the AS name of a result column of a SELECT statement is used as a logical term in the WHERE clause. Ticket a7b7803e8d1e869. SQLITE_SOURCE_ID: "2012-12-19 20:39:10 6b85b767d0ff7975146156a99ad673f2c1a23318" SHA1 for sqlite3.c: bbbaa68061e925bd4d7d18d7e1270935c5f7e39a

2012-12-12 (3.7.15)

Added the sqlite3_errstr() interface. Avoid invoking the sqlite3_trace() callback multiple times when a statement is automatically reprepared due to SQLITE_SCHEMA errors. Added support for Windows Phone 8 platforms Enhance IN operator processing to make use of indices with numeric affinities. Do full-table scans using covering indices when possible, under the theory that an index will be smaller and hence can be scanned with less I/O. Enhance the query optimizer so that ORDER BY clauses are more aggressively optimized, especially in joins where various terms of the ORDER BY clause come from separate tables of the join. Add the ability to implement FROM clause subqueries as coroutines rather that manifesting the subquery into a temporary table. Enhancements the command-line shell: Added the ".print" command Negative numbers in the ".width" command cause right-alignment Add the ".wheretrace" command when compiled with SQLITE_DEBUG Added the busy_timeout pragma. Added the instr() SQL function. Added the SQLITE_FCNTL_BUSYHANDLER file control, used to allow VFS implementations to get access to the busy handler callback. The xDelete method in the built-in VFSes now return SQLITE_IOERR_DELETE_NOENT if the file to be deleted does not exist. Enhanced support for QNX. Work around an optimizer bug in the MSVC compiler when targeting ARM. Bug fix: Avoid various concurrency problems in shared cache mode. Bug fix: Avoid a deadlock or crash if the backup API, shared cache, and the SQLite Encryption Extension are all used at once. Bug fix: SQL functions created using the TCL interface honor the "nullvalue" setting. Bug fix: Fix a 32-bit overflow problem on CREATE INDEX for databases larger than 16GB. Bug fix: Avoid segfault when using the COLLATE operator inside of a CHECK constraint or view in shared cache mode. SQLITE_SOURCE_ID: "2012-12-12 13:36:53 cd0b37c52658bfdf992b1e3dc467bae1835a94ae" SHA1 for sqlite3.c: 2b413611f5e3e3b6ef5f618f2a9209cdf25cbcff"

2012-10-04 (3.7.14.1)

Fix a bug (ticket [d02e1406a58ea02d]]) that causes a segfault on a LEFT JOIN that includes an OR in the ON clause. Work around a bug in the optimizer in the VisualStudio-2012 compiler that causes invalid code to be generated when compiling SQLite on ARM. Fix the TCL interface so that the "nullvalue" setting is honored for TCL implementations of SQL functions. SQLITE_SOURCE_ID: "2012-10-04 19:37:12 091570e46d04e84b67228e0bdbcd6e1fb60c6bdb" SHA1 for sqlite3.c: 62aaecaacab3a4bf4a8fe4aec1cfdc1571fe9a44

2012-09-03 (3.7.14)

Drop built-in support for OS/2. If you need to upgrade an OS/2 application to use this or a later version of SQLite, then add an application-defined VFS using the sqlite3_vfs_register() interface. The code removed in this release can serve as a baseline for the application-defined VFS. Ensure that floating point values are preserved exactly when reconstructing a database from the output of the ".dump" command of the command-line shell. Added the sqlite3_close_v2() interface. Updated the command-line shell so that it can be built using SQLITE_OMIT_FLOATING_POINT and SQLITE_OMIT_AUTOINIT. Improvements to the windows makefiles and build processes. Enhancements to PRAGMA integrity_check and PRAGMA quick_check so that they can optionally check just a single attached database instead of all attached databases. Enhancements to WAL mode processing that ensure that at least one valid read-mark is available at all times, so that read-only processes can always read the database. Performance enhancements in the sorter used by ORDER BY and CREATE INDEX. Added the SQLITE_DISABLE_FTS4_DEFERRED compile-time option. Better handling of aggregate queries where the aggregate functions are contained within subqueries. Enhance the query planner so that it will try to use a covering index on queries that make use of or optimization. SQLITE_SOURCE_ID: "2012-09-03 15:42:36 c0d89d4a9752922f9e367362366efde4f1b06f2a" SHA1 for sqlite3.c: 5fdf596b29bb426001f28b488ff356ae14d5a5a6

2012-06-11 (3.7.13)

In-memory databases that are specified using URI filenames are allowed to use shared cache, so that the same in-memory database can be accessed from multiple database connections. Recognize and use the mode=memory query parameter in URI filenames. Avoid resetting the schema of shared cache connections when any one connection closes. Instead, wait for the last connection to close before resetting the schema. In the RTREE extension, when rounding 64-bit floating point numbers to 32-bit for storage, always round in a direction that causes the bounding box to get larger. Adjust the unix driver to avoid unnecessary calls to fchown(). Add interfaces sqlite3_quota_ferror() and sqlite3_quota_file_available() to the test_quota.c module. The sqlite3_create_module() and sqlite3_create_module_v2() interfaces return SQLITE_MISUSE on any attempt to overload or replace a virtual table module. The destructor is always called in this case, in accordance with historical and current documentation. SQLITE_SOURCE_ID: "2012-06-11 02:05:22 f5b5a13f7394dc143aa136f1d4faba6839eaa6dc" SHA1 for sqlite3.c: ff0a771d6252545740ba9685e312b0e3bb6a641b

2012-05-22 (3.7.12.1)

Fix a bug (ticket c2ad16f997) in the 3.7.12 release that can cause a segfault for certain obscure nested aggregate queries. Fix various other minor test script problems. SQLITE_SOURCE_ID: "2012-05-22 02:45:53 6d326d44fd1d626aae0e8456e5fa2049f1ce0789" SHA1 for sqlite3.c: d494e8d81607f0515d4f386156fb0fd86d5ba7df

2012-05-14 (3.7.12)

Add the SQLITE_DBSTATUS_CACHE_WRITE option for sqlite3_db_status(). Optimize the typeof() and length() SQL functions so that they avoid unnecessary reading of database content from disk. Add the FTS4 "merge" command, the FTS4 "automerge" command, and the FTS4 "integrity-check" command. Report the name of specific CHECK constraints that fail. In the command-line shell, use popen() instead of fopen() if the first character of the argument to the ".output" command is "|". Make use of OVERLAPPED in the windows VFS to avoid some system calls and thereby obtain a performance improvement. More aggressive optimization of the AND operator when one side or the other is always false. Improved performance of queries with many OR-connected terms in the WHERE clause that can all be indexed. Add the SQLITE_RTREE_INT_ONLY compile-time option to force the R*Tree Extension Module to use integer instead of floating point values for both storage and computation. Enhance the PRAGMA integrity_check command to use much less memory when processing multi-gigabyte databases. New interfaces added to the test_quota.c add-on module. Added the ".trace" dot-command to the command-line shell. Allow virtual table constructors to be invoked recursively. Improved optimization of ORDER BY clauses on compound queries. Improved optimization of aggregate subqueries contained within an aggregate query. Bug fix: Fix the RELEASE command so that it does not cancel pending queries. This repairs a problem introduced in 3.7.11. Bug fix: Do not discard the DISTINCT as superfluous unless a subset of the result set is subject to a UNIQUE constraint and it none of the columns in that subset can be NULL. Ticket 385a5b56b9. Bug fix: Do not optimize away an ORDER BY clause that has the same terms as a UNIQUE index unless those terms are also NOT NULL. Ticket 2a5629202f. SQLITE_SOURCE_ID: "2012-05-14 01:41:23 8654aa9540fe9fd210899d83d17f3f407096c004" SHA1 for sqlite3.c: 57e2104a0f7b3f528e7f6b7a8e553e2357ccd2e1

2012-03-20 (3.7.11)

Enhance the INSERT syntax to allow multiple rows to be inserted via the VALUES clause. Enhance the CREATE VIRTUAL TABLE command to support the IF NOT EXISTS clause. Added the sqlite3_stricmp() interface as a counterpart to sqlite3_strnicmp(). Added the sqlite3_db_readonly() interface. Added the SQLITE_FCNTL_PRAGMA file control, giving VFS implementations the ability to add new PRAGMA statements or to override built-in PRAGMAs. Queries of the form: "SELECT max(x), y FROM table" returns the value of y on the same row that contains the maximum x value. Added support for the FTS4 languageid option. Documented support for the FTS4 content option. This feature has actually been in the code since version 3.7.9 but is only now considered to be officially supported. Pending statements no longer block ROLLBACK. Instead, the pending statement will return SQLITE_ABORT upon next access after the ROLLBACK. Improvements to the handling of CSV inputs in the command-line shell Fix a bug introduced in version 3.7.10 that might cause a LEFT JOIN to be incorrectly converted into an INNER JOIN if the WHERE clause indexable terms connected by OR. SQLITE_SOURCE_ID: "2012-03-20 11:35:50 00bb9c9ce4f465e6ac321ced2a9d0062dc364669" SHA1 for sqlite3.c: d460d7eda3a9dccd291aed2a9fda868b9b120a10

2012-01-16 (3.7.10)

The default schema format number is changed from 1 to 4. This means that, unless the PRAGMA legacy_file_format=ON statement is run, newly created database files will be unreadable by version of SQLite prior to 3.3.0 (2006-01-10). It also means that the descending indices are enabled by default. The sqlite3_pcache_methods structure and the SQLITE_CONFIG_PCACHE and SQLITE_CONFIG_GETPCACHE configuration parameters are deprecated. They are replaced by a new sqlite3_pcache_methods2 structure and SQLITE_CONFIG_PCACHE2 and SQLITE_CONFIG_GETPCACHE2 configuration parameters. Added the powersafe overwrite property to the VFS interface. Provide the SQLITE_IOCAP_POWERSAFE_OVERWRITE I/O capability, the SQLITE_POWERSAFE_OVERWRITE compile-time option, and the "psow=BOOLEAN" query parameter for URI filenames. Added the sqlite3_db_release_memory() interface and the shrink_memory pragma. Added the sqlite3_db_filename() interface. Added the sqlite3_stmt_busy() interface. Added the sqlite3_uri_boolean() and sqlite3_uri_int64() interfaces. If the argument to PRAGMA cache_size is negative N, that means to use approximately -1024*N bytes of memory for the page cache regardless of the page size. Enhanced the default memory allocator to make use of _msize() on windows, malloc_size() on Mac, and malloc_usable_size() on Linux. Enhanced the query planner to support index queries with range constraints on the rowid. Enhanced the query planner flattening logic to allow UNION ALL compounds to be promoted upwards to replace a simple wrapper SELECT even if the compounds are joins. Enhanced the query planner so that the xfer optimization can be used with INTEGER PRIMARY KEY ON CONFLICT as long as the destination table is initially empty. Enhanced the windows VFS so that all system calls can be overridden using the xSetSystemCall interface. Updated the "unix-dotfile" VFS to use locking directories with mkdir() and rmdir() instead of locking files with open() and unlink(). Enhancements to the test_quota.c extension to support stdio-like interfaces with quotas. Change the unix VFS to be tolerant of read() system calls that return less then the full number of requested bytes. Change both unix and windows VFSes to report a sector size of 4096 instead of the old default of 512. In the TCL Interface, add the -uri option to the "sqlite3" TCL command used for creating new database connection objects. Added the SQLITE_TESTCTRL_EXPLAIN_STMT test-control option with the SQLITE_ENABLE_TREE_EXPLAIN compile-time option to enable the command-line shell to display ASCII-art parse trees of SQL statements that it processes, for debugging and analysis. Bug fix: Add an additional xSync when restarting a WAL in order to prevent an exceedingly unlikely but theoretically possible database corruption following power-loss. Ticket ff5be73dee. Bug fix: Change the VDBE so that all registers are initialized to Invalid instead of NULL. Ticket 7bbfb7d442 Bug fix: Fix problems that can result from 32-bit integer overflow. Ticket ac00f496b7e2 SQLITE_SOURCE_ID: "2012-01-16 13:28:40 ebd01a8deffb5024a5d7494eef800d2366d97204" SHA1 for sqlite3.c: 6497cbbaad47220bd41e2e4216c54706e7ae95d4

2011-11-01 (3.7.9)

If a search token (on the right-hand side of the MATCH operator) in FTS4 begins with "^" then that token must be the first in its field of the document. ** Potentially Incompatible Change ** Added options SQLITE_DBSTATUS_CACHE_HIT and SQLITE_DBSTATUS_CACHE_MISS to the sqlite3_db_status() interface. Removed support for SQLITE_ENABLE_STAT2, replacing it with the much more capable SQLITE_ENABLE_STAT3 option. Enhancements to the sqlite3_analyzer utility program, including the --pageinfo and --stats options and support for multiplexed databases. Enhance the sqlite3_data_count() interface so that it can be used to determine if SQLITE_DONE has been seen on the prepared statement. Added the SQLITE_FCNTL_OVERWRITE file-control by which the SQLite core indicates to the VFS that the current transaction will overwrite the entire database file. Increase the default lookaside memory allocator allocation size from 100 to 128 bytes. Enhanced the query planner so that it can factor terms in and out of OR expressions in the WHERE clause in an effort to find better indices. Added the SQLITE_DIRECT_OVERFLOW_READ compile-time option, causing overflow pages to be read directly from the database file, bypassing the page cache. Remove limits on the magnitude of precision and width value in the format specifiers of the sqlite3_mprintf() family of string rendering routines. Fix a bug that prevent ALTER TABLE ... RENAME from working on some virtual tables in a database with a UTF16 encoding. Fix a bug in ASCII-to-float conversion that causes slow performance and incorrect results when converting numbers with ridiculously large exponents. Fix a bug that causes incorrect results in aggregate queries that use multiple aggregate functions whose arguments contain complicated expressions that differ only in the case of string literals contained within those expressions. Fix a bug that prevented the page_count and quick_check pragmas from working correctly if their names were capitalized. Fix a bug that caused VACUUM to fail if the count_changes pragma was engaged. Fix a bug in virtual table implementation that causes a crash if an FTS4 table is dropped inside a transaction and a SAVEPOINT occurs afterwards. SQLITE_SOURCE_ID: "2011-11-01 00:52:41 c7c6050ef060877ebe77b41d959e9df13f8c9b5e" SHA1 for sqlite3.c: becd16877f4f9b281b91c97e106089497d71bb47

2011-09-19 (3.7.8)

Orders of magnitude performance improvement for CREATE INDEX on very large tables. Improved the windows VFS to better defend against interference from anti-virus software. Improved query plan optimization when the DISTINCT keyword is present. Allow more system calls to be overridden in the unix VFS - to provide better support for chromium sandboxes. Increase the default size of a lookahead cache line from 100 to 128 bytes. Enhancements to the test_quota.c module so that it can track preexisting files. Bug fix: Virtual tables now handle IS NOT NULL constraints correctly. Bug fixes: Correctly handle nested correlated subqueries used with indices in a WHERE clause. SQLITE_SOURCE_ID: "2011-09-19 14:49:19 3e0da808d2f5b4d12046e05980ca04578f581177" SHA1 for sqlite3.c: bfcd74a655636b592c5dba6d0d5729c0f8e3b4de

2011-06-28 (3.7.7.1)

Fix a bug causing PRAGMA case_sensitive_like statements compiled using sqlite3_prepare() to fail with an SQLITE_SCHEMA error. SQLITE_SOURCE_ID: "2011-06-28 17:39:05 af0d91adf497f5f36ec3813f04235a6e195a605f" SHA1 for sqlite3.c: d47594b8a02f6cf58e91fb673e96cb1b397aace0

2011-06-23 (3.7.7)

2011-05-19 (3.7.6.3)

Fix a problem with WAL mode which could cause transactions to silently rollback if the cache_size is set very small (less than 10) and SQLite comes under memory pressure.

2011-04-17 (3.7.6.2)

Fix the function prototype for the open(2) system call to agree with POSIX. Without this fix, pthreads does not work correctly on NetBSD. SQLITE_SOURCE_ID: "2011-04-17 17:25:17 154ddbc17120be2915eb03edc52af1225eb7cb5e" SHA1 for sqlite3.c: 806577fd524dd5f3bfd8d4d27392ed2752bc9701

2011-04-13 (3.7.6.1)

Fix a bug in 3.7.6 that only appears if the SQLITE_FCNTL_SIZE_HINT file control is used with a build of SQLite that makes use of the HAVE_POSIX_FALLOCATE compile-time option and which has SQLITE_ENABLE_LOCKING_MODE turned off. SQLITE_SOURCE_ID: "2011-04-13 14:40:25 a35e83eac7b185f4d363d7fa51677f2fdfa27695" SHA1 for sqlite3.c: b81bfa27d3e09caf3251475863b1ce6dd9f6ab66

2011-04-12 (3.7.6)

Added the sqlite3_wal_checkpoint_v2() interface and enhanced the wal_checkpoint pragma to support blocking checkpoints. Improvements to the query planner so that it makes better estimates of plan costs and hence does a better job of choosing the right plan, especially when SQLITE_ENABLE_STAT2 is used. Fix a bug which prevented deferred foreign key constraints from being enforced when sqlite3_finalize() was not called by one statement with a failed foreign key constraint prior to another statement with foreign key constraints running. Integer arithmetic operations that would have resulted in overflow are now performed using floating-point instead. Increased the version number on the VFS object to 3 and added new methods xSetSysCall, xGetSysCall, and xNextSysCall used for doing full-coverage testing. Increase the maximum value of SQLITE_MAX_ATTACHED from 30 to 62 (though the default value remains at 10). Enhancements to FTS4: Added the fts4aux table Added support for compressed FTS4 content Enhance the ANALYZE command to support the name of an index as its argument, in order to analyze just that one index. Added the "unix-excl" built-in VFS on unix and unix-like platforms. SQLITE_SOURCE_ID: "2011-04-12 01:58:40 f9d43fa363d54beab6f45db005abac0a7c0c47a7" SHA1 for sqlite3.c: f38df08547efae0ff4343da607b723f588bbd66b

2011-02-01 (3.7.5)

Added the sqlite3_vsnprintf() interface. Added the SQLITE_DBSTATUS_LOOKASIDE_HIT, SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE, and SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL options for the sqlite3_db_status() interface. Added the SQLITE_OMIT_AUTORESET compile-time option. Added the SQLITE_DEFAULT_FOREIGN_KEYS compile-time option. Updates to sqlite3_stmt_readonly() so that its result is well-defined for all prepared statements and so that it works with VACUUM. Added the "-heap" option to the command-line shell Fix a bug involving frequent changes in and out of WAL mode and VACUUM that could (in theory) cause database corruption. Enhance the sqlite3_trace() mechanism so that nested SQL statements such as might be generated by virtual tables are shown but are shown in comments and without parameter expansion. This greatly improves tracing output when using the FTS3/4 and/or RTREE virtual tables. Change the xFileControl() methods on all built-in VFSes to return SQLITE_NOTFOUND instead of SQLITE_ERROR for an unrecognized operation code. The SQLite core invokes the SQLITE_FCNTL_SYNC_OMITTED file control to the VFS in place of a call to xSync if the database has PRAGMA synchronous set to OFF.

2010-12-07 (3.7.4)

2010-10-08 (3.7.3)

Added the sqlite3_create_function_v2() interface that includes a destructor callback. Added support for custom r-tree queries using application-supplied callback routines to define the boundary of the query region. The default page cache strives more diligently to avoid using memory beyond what is allocated to it by SQLITE_CONFIG_PAGECACHE. Or if using page cache is allocating from the heap, it strives to avoid going over the sqlite3_soft_heap_limit64(), even if SQLITE_ENABLE_MEMORY_MANAGEMENT is not set. Added the sqlite3_soft_heap_limit64() interface as a replacement for sqlite3_soft_heap_limit(). The ANALYZE command now gathers statistics on tables even if they have no indices. Tweaks to the query planner to help it do a better job of finding the most efficient query plan for each query. Enhanced the internal text-to-numeric conversion routines so that they work with UTF8 or UTF16, thereby avoiding some UTF16-to-UTF8 text conversions. Fix a problem that was causing excess memory usage with large WAL transactions in win32 systems. The interface between the VDBE and B-Tree layer is enhanced such that the VDBE provides hints to the B-Tree layer letting the B-Tree layer know when it is safe to use hashing instead of B-Trees for transient tables. Miscellaneous documentation enhancements.

2010-08-24 (3.7.2)

2010-08-23 (3.7.1)

Added new commands SQLITE_DBSTATUS_SCHEMA_USED and SQLITE_DBSTATUS_STMT_USED to the sqlite3_db_status() interface, in order to report out the amount of memory used to hold the schema and prepared statements of a connection. Increase the maximum size of a database pages from 32KiB to 64KiB. Use the LIKE optimization even if the right-hand side string contains no wildcards. Added the SQLITE_FCNTL_CHUNK_SIZE verb to the sqlite3_file_control() interface for both unix and windows, to cause database files to grow in large chunks in order to reduce disk fragmentation. Fixed a bug in the query planner that caused performance regressions relative to 3.6.23.1 on some complex joins. Fixed a typo in the OS/2 backend. Refactored the pager module. The SQLITE_MAX_PAGE_SIZE compile-time option is now silently ignored. The maximum page size is hard-coded at 65536 bytes.

2010-08-04 (3.7.0.1)

Fix a potential database corruption bug that can occur if version 3.7.0 and version 3.6.23.1 alternately write to the same database file. Ticket [51ae9cad317a1] Fix a performance regression related to the query planner enhancements of version 3.7.0.

2010-07-21 (3.7.0)

Added support for write-ahead logging. Query planner enhancement - automatic transient indices are created when doing so reduces the estimated query time. Query planner enhancement - the ORDER BY becomes a no-op if the query also contains a GROUP BY clause that forces the correct output order. Add the SQLITE_DBSTATUS_CACHE_USED verb for sqlite3_db_status(). The logical database size is now stored in the database header so that bytes can be appended to the end of the database file without corrupting it and so that SQLite will work correctly on systems that lack support for ftruncate().

2010-03-26 (3.6.23.1)

Fix a bug in the offsets() function of FTS3 Fix a missing "sync" that when omitted could lead to database corruption if a power failure or OS crash occurred just as a ROLLBACK operation was finishing.

2010-03-09 (3.6.23)

2010-01-06 (3.6.22)

Fix bugs that can (rarely) lead to incorrect query results when the CAST or OR operators are used in the WHERE clause of a query. Continuing enhancements and improvements to FTS3. Other miscellaneous bug fixes.

2009-12-07 (3.6.21)

The SQL output resulting from sqlite3_trace() is now modified to include the values of bound parameters. Performance optimizations targeting a specific use case from a single high-profile user of SQLite. A 12% reduction in the number of CPU operations is achieved (as measured by Valgrind). Actual performance improvements in practice may vary depending on workload. Changes include: The ifnull() and coalesce() SQL functions are now implemented using in-line VDBE code rather than calling external functions, so that unused arguments need never be evaluated. The substr() SQL function does not bother to measure the length its entire input string if it is only computing a prefix Unnecessary OP_IsNull, OP_Affinity, and OP_MustBeInt VDBE opcodes are suppressed Various code refactorizations for performance The FTS3 extension has undergone a major rework and cleanup. New FTS3 documentation is now available. The SQLITE_SECURE_DELETE compile-time option fixed to make sure that content is deleted even when the truncate optimization applies. Improvements to "dot-command" handling in the Command Line Interface. Other minor bug fixes and documentation enhancements.

2009-11-04 (3.6.20)

Optimizer enhancement: prepared statements are automatically re-compiled when a binding on the RHS of a LIKE operator changes or when any range constraint changes under SQLITE_ENABLE_STAT2. Various minor bug fixes and documentation enhancements.

2009-10-30 (3.6.16.1)

A small patch to version 3.6.16 to fix the OP_If bug.

2009-10-14 (3.6.19)

Added support for foreign key constraints. Foreign key constraints are disabled by default. Use the foreign_keys pragma to turn them on. Generalized the IS and IS NOT operators to take arbitrary expressions on their right-hand side. The TCL Interface has been enhanced to use the Non-Recursive Engine (NRE) interface to the TCL interpreter when linked against TCL 8.6 or later. Fix a bug introduced in 3.6.18 that can lead to a segfault when an attempt is made to write on a read-only database.

2009-09-11 (3.6.18)

Versioning of the SQLite source code has transitioned from CVS to Fossil. Query planner enhancements. The SQLITE_ENABLE_STAT2 compile-time option causes the ANALYZE command to collect a small histogram of each index, to help SQLite better select among competing range query indices. Recursive triggers can be enabled using the PRAGMA recursive_triggers statement. Delete triggers fire when rows are removed due to a REPLACE conflict resolution. This feature is only enabled when recursive triggers are enabled. Added the SQLITE_OPEN_SHAREDCACHE and SQLITE_OPEN_PRIVATECACHE flags for sqlite3_open_v2() used to override the global shared cache mode settings for individual database connections. Added improved version identification features: C-Preprocessor macro SQLITE_SOURCE_ID, C/C++ interface sqlite3_sourceid(), and SQL function sqlite_source_id(). Obscure bug fix on triggers ([efc02f9779]).

2009-08-10 (3.6.17)

Expose the sqlite3_strnicmp() interface for use by extensions and applications. Remove the restriction on virtual tables and shared cache mode. Virtual tables and shared cache can now be used at the same time. Many code simplifications and obscure bug fixes in support of providing 100% branch test coverage.

2009-06-27 (3.6.16)

Fix a bug (ticket #3929) that occasionally causes INSERT or UPDATE operations to fail on an indexed table that has a self-modifying trigger. Other minor bug fixes and performance optimizations.

2009-06-15 (3.6.15)

Refactor the internal representation of SQL expressions so that they use less memory on embedded platforms. Reduce the amount of stack space used Fix an 64-bit alignment bug on HP/UX and Sparc The sqlite3_create_function() family of interfaces now return SQLITE_MISUSE instead of SQLITE_ERROR when passed invalid parameter combinations. When new tables are created using CREATE TABLE ... AS SELECT ... the datatype of the columns is the simplified SQLite datatype (TEXT, INT, REAL, NUMERIC, or BLOB) instead of a copy of the original datatype from the source table. Resolve race conditions when checking for a hot rollback journal. The sqlite3_shutdown() interface frees all mutexes under windows. Enhanced robustness against corrupt database files Continuing improvements to the test suite and fixes to obscure bugs and inconsistencies that the test suite improvements are uncovering.

2009-05-25 (3.6.14.2)

Fix a code generator bug introduced in version 3.6.14. This bug can cause incorrect query results under obscure circumstances. Ticket #3879.

2009-05-19 (3.6.14.1)

Fix a bug in group_concat(), ticket #3841 Fix a performance bug in the pager cache, ticket #3844 Fix a bug in the sqlite3_backup implementation that can lead to a corrupt backup database. Ticket #3858.

2009-05-07 (3.6.14)

Added the optional asynchronous VFS module. Enhanced the query optimizer so that virtual tables are able to make use of OR and IN operators in the WHERE clause. Speed improvements in the btree and pager layers. Added the SQLITE_HAVE_ISNAN compile-time option which will cause the isnan() function from the standard math library to be used instead of SQLite's own home-brew NaN checker. Countless minor bug fixes, documentation improvements, new and improved test cases, and code simplifications and cleanups.

2009-04-13 (3.6.13)

Fix a bug in version 3.6.12 that causes a segfault when running a count(*) on the sqlite_master table of an empty database. Ticket #3774. Fix a bug in version 3.6.12 that causes a segfault that when inserting into a table using a DEFAULT value where there is a function as part of the DEFAULT value expression. Ticket #3791. Fix data structure alignment issues on Sparc. Ticket #3777. Other minor bug fixes.

2009-03-31 (3.6.12)

Fixed a bug that caused database corruption when an incremental_vacuum is rolled back in an in-memory database. Ticket #3761. Added the sqlite3_unlock_notify() interface. Added the reverse_unordered_selects pragma. The default page size on windows is automatically adjusted to match the capabilities of the underlying filesystem. Add the new ".genfkey" command in the CLI for generating triggers to implement foreign key constraints. Performance improvements for "count(*)" queries. Reduce the amount of heap memory used, especially by TRIGGERs.

2009-02-18 (3.6.11)

Added the hot-backup interface. Added new commands ".backup" and ".restore" to the CLI. Added new methods backup and restore to the TCL interface. Improvements to the syntax bubble diagrams Various minor bug fixes

2009-01-15 (3.6.10)

Fix a cache coherency problem that could lead to database corruption. Ticket #3584.

2009-01-14 (3.6.9)

Fix two bugs, which when combined might result in incorrect query results. Both bugs were harmless by themselves; only when they team up do they cause problems. Ticket #3581.

2009-01-12 (3.6.8)

Added support for nested transactions Enhanced the query optimizer so that it is able to use multiple indices to efficiently process OR-connected constraints in a WHERE clause. Added support for parentheses in FTS3 query patterns using the SQLITE_ENABLE_FTS3_PARENTHESIS compile-time option.

2008-12-16 (3.6.7)

Reorganize the Unix interface in os_unix.c Added support for "Proxy Locking" on Mac OS X. Changed the prototype of the sqlite3_auto_extension() interface in a way that is backwards compatible but which might cause warnings in new builds of applications that use that interface. Changed the signature of the xDlSym method of the sqlite3_vfs object in a way that is backwards compatible but which might cause compiler warnings. Added superfluous casts and variable initializations in order to suppress nuisance compiler warnings. Fixes for various minor bugs.

2008-11-26 (3.6.6.2)

Fix a bug in the b-tree delete algorithm that seems like it might be able to cause database corruption. The bug was first introduced in version 3.6.6 by check-in [5899] on 2008-11-13. Fix a memory leak that can occur following a disk I/O error.

2008-11-22 (3.6.6.1)

Fix a bug in the page cache that can lead database corruption following a rollback. This bug was first introduced in version 3.6.4. Two other very minor bug fixes

2008-11-19 (3.6.6)

Fix a #define that prevented memsys5 from compiling Fix a problem in the virtual table commit mechanism that was causing a crash in FTS3. Ticket #3497. Add the application-defined page cache Added built-in support for VxWorks

2008-11-12 (3.6.5)

2008-10-15 (3.6.4)

Add option support for LIMIT and ORDER BY clauses on DELETE and UPDATE statements. Only works if SQLite is compiled with SQLITE_ENABLE_UPDATE_DELETE_LIMIT. Added the sqlite3_stmt_status() interface for performance monitoring. Add the INDEXED BY clause. The LOCKING_STYLE extension is now enabled by default on Mac OS X Added the TRUNCATE option to PRAGMA journal_mode Performance enhancements to tree balancing logic in the B-Tree layer. Added the source code and documentation for the genfkey program for automatically generating triggers to enforce foreign key constraints. Added the SQLITE_OMIT_TRUNCATE_OPTIMIZATION compile-time option. The SQL language documentation is converted to use syntax diagrams instead of BNF. Other minor bug fixes

2008-09-22 (3.6.3)

Fix for a bug in the SELECT DISTINCT logic that was introduced by the prior version. Other minor bug fixes

2008-08-30 (3.6.2)

Split the pager subsystem into separate pager and pcache subsystems. Factor out identifier resolution procedures into separate files. Bug fixes

2008-08-06 (3.6.1)

Added the lookaside memory allocator for a speed improvement in excess of 15% on some workloads. (Your mileage may vary.) Added the SQLITE_CONFIG_LOOKASIDE verb to sqlite3_config() to control the default lookaside configuration. Added verbs SQLITE_STATUS_PAGECACHE_SIZE and SQLITE_STATUS_SCRATCH_SIZE to the sqlite3_status() interface. Modified SQLITE_CONFIG_PAGECACHE and SQLITE_CONFIG_SCRATCH to remove the "+4" magic number in the buffer size computation. Added the sqlite3_db_config() and sqlite3_db_status() interfaces for controlling and monitoring the lookaside allocator separately on each database connection. Numerous other performance enhancements Miscellaneous minor bug fixes

2008-07-16 (3.6.0 beta)

Modifications to the virtual file system interface to support a wider range of embedded systems. See 35to36.html for additional information. *** Potentially incompatible change *** All C-preprocessor macros used to control compile-time options now begin with the prefix "SQLITE_". This may require changes to applications that compile SQLite using their own makefiles and with custom compile-time options, hence we mark this as a *** Potentially incompatible change *** The SQLITE_MUTEX_APPDEF compile-time option is no longer supported. Alternative mutex implementations can now be added at run-time using the sqlite3_config() interface with the SQLITE_CONFIG_MUTEX verb. *** Potentially incompatible change *** The handling of IN and NOT IN operators that contain a NULL on their right-hand side expression is brought into compliance with the SQL standard and with other SQL database engines. This is a bug fix, but as it has the potential to break legacy applications that depend on the older buggy behavior, we mark that as a *** Potentially incompatible change *** The result column names generated for compound subqueries have been simplified to show only the name of the column of the original table and omit the table name. This makes SQLite operate more like other SQL database engines. Added the sqlite3_config() interface for doing run-time configuration of the entire SQLite library. Added the sqlite3_status() interface used for querying run-time status information about the overall SQLite library and its subsystems. Added the sqlite3_initialize() and sqlite3_shutdown() interfaces. The SQLITE_OPEN_NOMUTEX option was added to sqlite3_open_v2(). Added the PRAGMA page_count command. Added the sqlite3_next_stmt() interface. Added a new R*Tree virtual table

2008-05-14 (3.5.9)

Added experimental support for the journal_mode PRAGMA and persistent journal. Journal mode PERSIST is the default behavior in exclusive locking mode. Fix a performance regression on LEFT JOIN (see ticket #3015) that was mistakenly introduced in version 3.5.8. Performance enhancement: Reengineer the internal routines used to interpret and render variable-length integers. Fix a buffer-overrun problem in sqlite3_mprintf() which occurs when a string without a zero-terminator is passed to "%.*s". Always convert IEEE floating point NaN values into NULL during processing. (Ticket #3060) Make sure that when a connection blocks on a RESERVED lock that it is able to continue after the lock is released. (Ticket #3093) The "configure" scripts should now automatically configure Unix systems for large file support. Improved error messages for when large files are encountered and large file support is disabled. Avoid cache pages leaks following disk-full or I/O errors And, many more minor bug fixes and performance enhancements....

2008-04-16 (3.5.8)

Expose SQLite's internal pseudo-random number generator (PRNG) via the sqlite3_randomness() interface New interface sqlite3_context_db_handle() that returns the database connection handle that has invoked an application-defined SQL function. New interface sqlite3_limit() allows size and length limits to be set on a per-connection basis and at run-time. Improved crash-robustness: write the database page size into the rollback journal header. Allow the VACUUM command to change the page size of a database file. The xAccess() method of the VFS is allowed to return -1 to signal a memory allocation error. Performance improvement: The OP_IdxDelete opcode uses unpacked records, obviating the need for one OP_MakeRecord opcode call for each index record deleted. Performance improvement: Constant subexpressions are factored out of loops. Performance improvement: Results of OP_Column are reused rather than issuing multiple OP_Column opcodes. Fix a bug in the RTRIM collating sequence. Fix a bug in the SQLITE_SECURE_DELETE option that was causing Firefox crashes. Make arrangements to always test SQLITE_SECURE_DELETE prior to each release. Other miscellaneous performance enhancements. Other miscellaneous minor bug fixes.

2008-03-17 (3.5.7)

Fix a bug (ticket #2927) in the register allocation for compound selects - introduced by the new VM code in version 3.5.5. ALTER TABLE uses double-quotes instead of single-quotes for quoting filenames. Use the WHERE clause to reduce the size of a materialized VIEW in an UPDATE or DELETE statement. (Optimization) Do not apply the flattening optimization if the outer query is an aggregate and the inner query contains ORDER BY. (Ticket #2943) Additional OS/2 updates Added an experimental power-of-two, first-fit memory allocator. Remove all instances of sprintf() from the code Accept "Z" as the zulu timezone at the end of date strings Fix a bug in the LIKE optimizer that occurs when the last character before the first wildcard is an upper-case "Z" Added the "bitvec" object for keeping track of which pages have been journalled. Improves speed and reduces memory consumption, especially for large database files. Get the SQLITE_ENABLE_LOCKING_STYLE macro working again on Mac OS X. Store the statement journal in the temporary file directory instead of collocated with the database file. Many improvements and cleanups to the configure script

2008-02-06 (3.5.6)

Fix a bug (ticket #2913) that prevented virtual tables from working in a LEFT JOIN. The problem was introduced into shortly before the 3.5.5 release. Bring the OS/2 porting layer up-to-date. Add the new sqlite3_result_error_code() API and use it in the implementation of ATTACH so that proper error codes are returned when an ATTACH fails.

2008-01-31 (3.5.5)

Convert the underlying virtual machine to be a register-based machine rather than a stack-based machine. The only user-visible change is in the output of EXPLAIN. Add the build-in RTRIM collating sequence.

2007-12-14 (3.5.4)

Fix a critical bug in UPDATE or DELETE that occurs when an OR REPLACE clause or a trigger causes rows in the same table to be deleted as side effects. (See ticket #2832.) The most likely result of this bug is a segmentation fault, though database corruption is a possibility. Bring the processing of ORDER BY into compliance with the SQL standard for case where a result alias and a table column name are in conflict. Correct behavior is to prefer the result alias. Older versions of SQLite incorrectly picked the table column. (See ticket #2822.) The VACUUM command preserves the setting of the legacy_file_format pragma. (Ticket #2804.) Productize and officially support the group_concat() SQL function. Better optimization of some IN operator expressions. Add the ability to change the auto_vacuum status of a database by setting the auto_vaccum pragma and VACUUMing the database. Prefix search in FTS3 is much more efficient. Relax the SQL statement length restriction in the CLI so that the ".dump" output of databases with very large BLOBs and strings can be played back to recreate the database. Other small bug fixes and optimizations.

2007-11-27 (3.5.3)

Move website and documentation files out of the source tree into a separate CM system. Fix a long-standing bug in INSERT INTO ... SELECT ... statements where the SELECT is compound. Fix a long-standing bug in RAISE(IGNORE) as used in BEFORE triggers. Fixed the operator precedence for the ~ operator. On Win32, do not return an error when attempting to delete a file that does not exist. Allow collating sequence names to be quoted. Modify the TCL interface to use sqlite3_prepare_v2(). Fix multiple bugs that can occur following a malloc() failure. sqlite3_step() returns SQLITE_MISUSE instead of crashing when called with a NULL parameter. FTS3 now uses the SQLite memory allocator exclusively. The FTS3 amalgamation can now be appended to the SQLite amalgamation to generate a super-amalgamation containing both. The DISTINCT keyword now will sometimes use an INDEX if an appropriate index is available and the optimizer thinks its use might be advantageous.

2007-11-05 (3.5.2)

Dropped support for the SQLITE_OMIT_MEMORY_ALLOCATION compile-time option. Always open files using FILE_FLAG_RANDOM_ACCESS under Windows. The 3rd parameter of the built-in SUBSTR() function is now optional. Bug fix: do not invoke the authorizer when reparsing the schema after a schema change. Added the experimental malloc-free memory allocator in mem3.c. Virtual machine stores 64-bit integer and floating point constants in binary instead of text for a performance boost. Fix a race condition in test_async.c. Added the ".timer" command to the CLI

2007-10-04 (3.5.1)

Nota Bene: We are not using terms "alpha" or "beta" on this release because the code is stable and because if we use those terms, nobody will upgrade. However, we still reserve the right to make incompatible changes to the new VFS interface in future releases. Fix a bug in the handling of SQLITE_FULL errors that could lead to database corruption. Ticket #2686. The test_async.c drive now does full file locking and works correctly when used simultaneously by multiple processes on the same database. The CLI ignores whitespace (including comments) at the end of lines Make sure the query optimizer checks dependencies on all terms of a compound SELECT statement. Ticket #2640. Add demonstration code showing how to build a VFS for a raw mass storage without a filesystem. Added an output buffer size parameter to the xGetTempname() method of the VFS layer. Sticky SQLITE_FULL or SQLITE_IOERR errors in the pager are reset when a new transaction is started.

2007-09-04 (3.5.0) alpha

Redesign the OS interface layer. See 34to35.html for details. *** Potentially incompatible change *** The sqlite3_release_memory(), sqlite3_soft_heap_limit(), and sqlite3_enable_shared_cache() interfaces now work cross all threads in the process, not just the single thread in which they are invoked. *** Potentially incompatible change *** Added the sqlite3_open_v2() interface. Reimplemented the memory allocation subsystem and made it replaceable at compile-time. Created a new mutex subsystem and made it replicable at compile-time. The same database connection may now be used simultaneously by separate threads.

2007-08-13 (3.4.2)

Fix a database corruption bug that might occur if a ROLLBACK command is executed in auto-vacuum mode and a very small sqlite3_soft_heap_limit is set. Ticket #2565. Add the ability to run a full regression test with a small sqlite3_soft_heap_limit. Fix other minor problems with using small soft heap limits. Work-around for GCC bug 32575. Improved error detection of misused aggregate functions. Improvements to the amalgamation generator script so that all symbols are prefixed with either SQLITE_PRIVATE or SQLITE_API.

2007-07-20 (3.4.1)

Fix a bug in VACUUM that can lead to database corruptio if two processes are connected to the database at the same time and one VACUUMs then the other then modifies the database. The expression "+column" is now considered the same as "column" when computing the collating sequence to use on the expression. In the TCL language interface, "@variable" instead of "$variable" always binds as a blob. Added PRAGMA freelist_count for determining the current size of the freelist. The PRAGMA auto_vacuum=incremental setting is now persistent. Add FD_CLOEXEC to all open files under Unix. Fix a bug in the min()/max() optimization when applied to descending indices. Make sure the TCL language interface works correctly with 64-bit integers on 64-bit machines. Allow the value -9223372036854775808 as an integer literal in SQL statements. Add the capability of "hidden" columns in virtual tables. Use the macro SQLITE_PRIVATE (defaulting to