*** DRAFT ***
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.
- 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
- 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.
- 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
- 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.
- SQLITE_SOURCE_ID: "2016-05-18 10:57:30 fc49f556e48970561d7ab6a2f24fdd7d9eb81ff2"
- SHA1 for sqlite3.c: 9b9171b1e6ce7a980e6b714e9c0d9112657ad552
Bug fixes backported into patch release 3.8.8 (2015-01-16):
- Added the PRAGMA data_version command that can be used to determine if
a database file has been modified by another process.
- Added the SQLITE_CHECKPOINT_TRUNCATE option to the
sqlite3_wal_checkpoint_v2() interface, with corresponding enhancements
to PRAGMA wal_checkpoint.
- Added the sqlite3_stmt_scanstatus() interface, available only when
compiled with SQLITE_ENABLE_STMT_SCANSTATUS.
- The sqlite3_table_column_metadata() is enhanced to work correctly on
WITHOUT ROWID tables and to check for the existence of a
a table if the column name parameter is NULL. The interface is now
also included in the build by default, without requiring
the SQLITE_ENABLE_COLUMN_METADATA compile-time option.
- Added the SQLITE_ENABLE_API_ARMOR compile-time option.
- Added the SQLITE_REVERSE_UNORDERED_SELECTS compile-time option.
- Added the SQLITE_SORTER_PMASZ compile-time option and SQLITE_CONFIG_PMASZ
- Added the SQLITE_CONFIG_PCACHE_HDRSZ option to sqlite3_config()
which makes it easier for applications to determine the appropriate
amount of memory for use with SQLITE_CONFIG_PAGECACHE.
- The number of rows in a VALUES clause is no longer limited by
- Added the eval.c
loadable extension that implements an eval() SQL function that will recursively
- Reduce the number of memcpy() operations involved in balancing a b-tree,
for 3.2% overall performance boost.
- Improvements to cost estimates for the skip-scan optimization.
- The automatic indexing optimization is now capable of generating
a partial index if that is appropriate.
- Ensure durability following a power loss with
"PRAGMA journal_mode=TRUNCATE" by calling fsync() right after truncating
the journal file.
- The query planner now recognizes that any column in the right-hand
table of a LEFT JOIN can be NULL, even if that column has a NOT NULL
constraint. Avoid trying to optimize out NULL tests in those cases.
Fix for ticket
- Make sure ORDER BY puts rows in ascending order even if the DISTINCT
operator is implemented using a descending index. Fix for ticket
- Fix data races that might occur under stress when running with many threads
in shared cache mode where some of the threads are opening and
- Fix obscure crash bugs found by
american fuzzy lop. Ticket
- Work around a GCC optimizer bug (for gcc 4.2.1 on MacOS 10.7) that caused the
R-Tree extension to compute incorrect results when compiled with -O3.
- Disable the use of the strchrnul() C-library routine unless it is
specifically enabled using the -DHAVE_STRCHRNULL compile-time option.
- Improvements to the effectiveness and accuracy of the
likelihood(), likely(), and unlikely() SQL hint functions.
Bug fixes backported into patch release 22.214.171.124 (2014-12-09):
- Bug fix: Add in a mutex that was omitted from the previous 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.
*** DRAFT ***