Small. Fast. Reliable.
Choose any three.

## SQLite Release 3.13.0 On 2016-05-18

1. Postpone I/O associated with TEMP files for as long as possible, with the hope that the I/O can ultimately be avoided completely.
2. Merged the session extension into trunk.
3. Added the ".auth ON|OFF" command to the command-line shell.
4. Added the "--indent" option to the ".schema" and ".fullschema" commands of the command-line shell, to turn on pretty-printing.
5. Added the ".eqp full" option to the command-line shell, that does both EXPLAIN and EXPLAIN QUERY PLAN on each statement that is evaluated.
6. Improved unicode filename handling in the command-line shell on Windows.
7. Improved resistance against goofy query planner decisions caused by incomplete or incorrect modifications to the sqlite_stat1 table by the application.
8. 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.
9. 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:

10. 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
11. 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.
12. 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.
13. 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:

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

    Bug fixes backported into patch release 3.8.4.1 (2014-03-11):

16. Work around a C-preprocessor macro conflict that breaks the build for some configurations with Microsoft Visual Studio.
17. When computing the cost of the skip-scan optimization, take into account the fact that multiple seeks are required.

    Bug fixes backported into patch release 3.8.4 (2014-03-10):

18. Code optimization and refactoring for improved performance.
19. Add the ".clone" and ".save" commands to the command-line shell.
20. Update the banner on the command-line shell to alert novice users when they are using an ephemeral in-memory database.
21. Fix editline support in the command-line shell.
22. Add support for coverage testing of VDBE programs using the SQLITE_TESTCTRL_VDBE_COVERAGE verb of sqlite3_test_control().
23. Update the _FILE_OFFSET_BITS macro so that builds work again on QNX.
24. Change the datatype of SrcList.nSrc from type u8 to type int to work around an issue in the C compiler on AIX.
25. Get extension loading working on Cygwin.
26. 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.
27. Bug fix: DISTINCT now recognizes that a zeroblob and a blob of all 0x00 bytes are the same thing. Ticket [fccbde530a]
28. 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]
29. Bug fix: Make sure "rowid" columns are correctly resolved in joins between normal tables and WITHOUT ROWID tables. Ticket [c34d0557f7]
30. 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]
31. Bug fix: Ensure that "ORDER BY random()" clauses do not get optimized out. Ticket [65bdeb9739]
32. Bug fix: Repair a name-resolution error that can occur in sub-select statements contained within a TRIGGER. Ticket [4ef7e3cfca]
33. 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.

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.