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.12.0 (2016-03-29):

  Potentially Disruptive Change:

- The SQLITE_DEFAULT_PAGE_SIZE is increased from 1024 to 4096. The SQLITE_DEFAULT_CACHE_SIZE is changed from 2000 to -2000 so the same amount of cache memory is used by default. See the application note on the version 3.12.0 page size change for further information.

  Performance enhancements:

- Enhancements to the Lemon parser generator so that it creates a smaller and faster SQL parser.
- Only create master journal files if two or more attached databases are all modified, do not have PRAGMA synchronous set to OFF, and do not have the journal_mode set to OFF, MEMORY, or WAL.
- Only create statement journal files when their size exceeds a threshold. Otherwise the journal is held in memory and no I/O occurs. The threshold can be configured at compile-time using SQLITE_STMTJRNL_SPILL or at start-time using sqlite3_config(SQLITE_CONFIG_STMTJRNL_SPILL).
- The query planner is able to optimize IN operators on virtual tables even if the xBestIndex method does not set the sqlite3_index_constraint_usage.omit flag of the virtual table column to the left of the IN operator.
- The query planner now does a better job of optimizing virtual table accesses in a 3-way or higher join where constraints on the virtual table are split across two or more other tables of the join.
- More efficient handling of application-defined SQL functions, especially in cases where the application defines hundreds or thousands of custom functions.
- The query planner considers the LIMIT clause when estimating the cost of ORDER BY.
- The configure script (on unix) automatically detects pread() and pwrite() and sets compile-time options to use those OS interfaces if they are available.
- Reduce the amount of memory needed to hold the schema.
- Other miscellaneous micro-optimizations for improved performance and reduced memory usage.

  New Features:

- Added the SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER option to sqlite3_db_config() which allows the two-argument version of the fts3_tokenizer() SQL function to be enabled or disabled at run-time.
- Added the sqlite3rbu_bp_progress() interface to the RBU extension.
- The PRAGMA defer_foreign_keys=ON statement now also disables RESTRICT actions on foreign key.
- Added the sqlite3_system_errno() interface.
- Added the SQLITE_DEFAULT_SYNCHRONOUS and SQLITE_DEFAULT_WAL_SYNCHRONOUS compile-time options. The SQLITE_DEFAULT_SYNCHRONOUS compile-time option replaces the SQLITE_EXTRA_DURABLE option, which is no longer supported.
- Enhanced the ".stats" command in the command-line shell to show more information about I/O performance obtained from /proc, when available.

  Bug fixes:

- Make sure the sqlite3_set_auxdata() values from multiple triggers within a single statement do not interfere with one another. Ticket dc9b1c91.
- Fix the code generator for expressions of the form "x IN (SELECT...)" where the SELECT statement on the RHS is a correlated subquery. Ticket 5e3c886796e5512e.
- Fix a harmless TSAN warning associated with the sqlite3_db_readonly() interface.

  Bug fixes backported into patch release 3.11.1 (2016-03-03):

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

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.