sqlite-autoconf-3090000 (3.9.0)

[Fernando de Oliveira]

​https://www.sqlite.org/2015/sqlite-autoconf-3090000.tar.gz

​https://www.sqlite.org/2015/sqlite-doc-3090000.zip

​https://www.sqlite.org/download.html

sqlite-autoconf-3090000.tar.gz sha1: 6578aa8df05fd7777fbbc4fbf1912d981623f73b

sqlite-doc-3090000.zip sha1: f20c4904ae55e2ef106bb0ecf31256b3e5d3b3ee

​https://www.sqlite.org/releaselog/3_9_0.html

SQLite Release 3.9.0 On 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.

[Fernando de Oliveira]

Fixed at r16527.