Small. Fast. Reliable.
Choose any three.
Search for:

## SQLite Release 3.13.0 On 2016-05-18

- Postpone I/O associated with TEMP files for as long as possible, with the hope that the I/O can ultimately be avoided completely.
- Merged the session extension into trunk.
- Added the ".auth ON|OFF" command to the command-line shell.
- Added the "--indent" option to the ".schema" and ".fullschema" commands of the command-line shell, to turn on pretty-printing.
- Added the ".eqp full" option to the command-line shell, that does both EXPLAIN and EXPLAIN QUERY PLAN on each statement that is evaluated.
- Improved unicode filename handling in the command-line shell on Windows.
- Improved resistance against goofy query planner decisions caused by incomplete or incorrect modifications to the sqlite_stat1 table by the application.
- Added the sqlite3_db_config(db,SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION) interface which allows the sqlite3_load_extension() C-API to be enabled while keeping the load_extension() SQL function disabled for security.
- Change the temporary directory search algorithm on Unix to allow directories with write and execute permission, but without read permission, to serve as temporary directories. Apply this same standard to the "." fallback directory.

  Bug Fixes:

- Fix a problem with the multi-row one-pass DELETE optimization that was causing it to compute incorrect answers with a self-referential subquery in the WHERE clause. Fix for ticket dc6ebeda9396087
- Fix a possible segfault with DELETE when table is a rowid table with an INTEGER PRIMARY KEY and the WHERE clause contains a OR and the table has one or more indexes that are able to trigger the OR optimization, but none of the indexes reference any table columns other than the INTEGER PRIMARY KEY. Ticket 16c9801ceba49.
- When checking for the WHERE-clause push-down optimization, verify that all terms of the compound inner SELECT are non-aggregate, not just the last term. Fix for ticket f7f8c97e97597.
- Fix a locking race condition in Windows that can occur when two or more processes attempt to recover the same hot journal at the same time.

  Hashes:

- SQLITE_SOURCE_ID: "2016-05-18 10:57:30 fc49f556e48970561d7ab6a2f24fdd7d9eb81ff2"
- SHA1 for sqlite3.c: 9b9171b1e6ce7a980e6b714e9c0d9112657ad552

  Bug fixes backported into patch release 3.9.0 (2015-10-14):

  Policy Changes:

- The version numbering conventions for SQLite are revised to use the emerging standard of semantic versioning.

  New Features And Enhancements:

- Added the json1 extension module in the source tree, and in the amalgamation. Enable support using the SQLITE_ENABLE_JSON1 compile-time option.
- Added Full Text Search version 5 (FTS5) to the amalgamation, enabled using SQLITE_ENABLE_FTS5. FTS5 will be considered "experimental" (subject to incompatible changes) for at least one more release cycle.
- The CREATE VIEW statement now accepts an optional list of column names following the view name.
- Added support for indexes on expressions.
- Added support for table-valued functions in the FROM clause of a SELECT statement.
- Added support for eponymous virtual tables.
- A VIEW may now reference undefined tables and functions when initially created. Missing tables and functions are reported when the VIEW is used in a query.
- Added the sqlite3_value_subtype() and sqlite3_result_subtype() interfaced (used by the json1 extension).
- The query planner is now able to use partial indexes that contain AND-connected terms in the WHERE clause.
- The sqlite3_analyzer.exe utility is updated to report the depth of each btree and to show the average fanout for indexes and WITHOUT ROWID tables.
- Enhanced the dbstat virtual table so that it can be used as a table-valued function where the argument is the schema to be analyzed.

  Other changes:

- The sqlite3_memory_alarm() interface, which has been deprecated and undocumented for 8 years, is changed into a no-op.

  Important fixes:

- Fixed a critical bug in the SQLite Encryption Extension that could cause the database to become unreadable and unrecoverable if a VACUUM command changed the size of the encryption nonce.
- Added a memory barrier in the implementation of sqlite3_initialize() to help ensure that it is thread-safe.
- Fix the OR optimization so that it always ignores subplans that do not use an index.
- Do not apply the WHERE-clause pushdown optimization on terms that originate in the ON or USING clause of a LEFT JOIN. Fix for ticket c2a19d81652f40568c.

  Bug fixes backported into patch release 3.8.11.1 (2015-07-29):

- 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.

A complete list of SQLite releases in a single page and a chronology are both also available. A detailed history of every check-in is available at SQLite version control site.