May 15th, 2012· Add the SQLITE_DBSTATUS_CACHE_WRITE option for sqlite3_db_status().
· Optimize the typeof() and length() SQL functions so that they avoid unnecessary reading of database content from disk.
· Add the FTS4 "merge" command, the FTS4 "automerge" command, and the FTS4 "integrity-check" command.
· Report the name of specific CHECK constraints that fail.
· In the command-line shell, use popen() instead of fopen() if the first character of the argument to the ".output" command is "|".
· Make use of OVERLAPPED in the windows VFS to avoid some system calls and thereby obtain a performance improvement.
· More aggressive optimization of the AND operator when one side or the other is always false.
· Improved performance of queries with many OR-connected terms in the WHERE clause that can all be indexed.
· Add the SQLITE_RTREE_INT_ONLY compile-time option to force the R*Tree Extension Module to use integer instead of floating point values for both storage and computation.
· Enhance the PRAGMA integrity_check command to use much less memory when processing multi-gigabyte databases.
· New interfaces added to the test_quota.c add-on module.
· Added the ".trace" dot-command to the command-line shell.
· Allow virtual table constructors to be invoked recursively.
· Improved optimization of ORDER BY clauses on compound queries.
· Improved optimization of aggregate subqueries contained within an aggregate query.
· Bug fix: Fix the RELEASE command so that it does not cancel pending queries. This repairs a problem introduced in 3.7.11.
· Bug fix: Do not discard the DISTINCT as superfluous unless a subset of the result set is subject to a UNIQUE constraint and it none of the columns in that subset can be NULL. Ticket 385a5b56b9.
· Bug fix: Do not optimize away an ORDER BY clause that has the same terms as a UNIQUE index unless those terms are also NOT NULL. Ticket 2a5629202f.
· SQLITE_SOURCE_ID: "2012-05-14 01:41:23 8654aa9540fe9fd210899d83d17f3f407096c004"
· SHA1 for sqlite3.c: 57e2104a0f7b3f528e7f6b7a8e553e2357ccd2e1
March 21st, 2012· Enhance the INSERT syntax to allow multiple rows to be inserted via the VALUES clause.
· Enhance the CREATE VIRTUAL TABLE command to support the IF NOT EXISTS clause.
· Added the sqlite3_stricmp() interface as a counterpart to sqlite3_strnicmp().
· Added the sqlite3_db_readonly() interface.
· Added the SQLITE_FCNTL_PRAGMA file control, giving VFS implementations the ability to add new PRAGMA statements or to override built-in PRAGMAs.
· Queries of the form: "SELECT max(x), y FROM table" returns the value of y on the same row that contains the maximum x value.
· Added support for the FTS4 languageid option.
· Documented support for the FTS4 content option. This feature has actually been in the code since version 3.7.9 but is only now considered to be officially supported.
· Pending statements no longer block ROLLBACK. Instead, the pending statement will return SQLITE_ABORT upon next access after the ROLLBACK.
· Improvements to the handling of CSV inputs in the command-line shell
· Fix a bug introduced in version 3.7.10 that might cause a LEFT JOIN to be incorrectly converted into an INNER JOIN if the WHERE clause indexable terms connected by OR.
February 8th, 2012· The SQLITE_CONFIG_PCACHE mechanism has been replaced with SQLITE_CONFIG_PCACHE2. If you do not know what this mechanism is (it is an extreme corner-case and is seldom used) then this change will not effect you in the least
· The default schema format number for new database files has changed from 1 to 4. SQLite has been able to generate and read database files using schema format 4 for six years. But up unto now, the default schema format has been 1 so that older versions of SQLite could read and write databases generated by newer versions of SQLite. But those older versions of SQLite have become so scarce now that it seems reasonable to make the new format the default
· SQLite is changing some of the assumptions it makes above the behavior of disk drives and flash memory devices during a sudden power loss. This change is completely transparent to applications. Read about the powersafe overwrite property for additional information
· Lots of new interfaces have been added in this release
· sqlite3_db_release_memory()
· PRAGMA shrink_memory
· sqlite3_db_filename()
· sqlite3_stmt_busy()
· sqlite3_uri_boolean()
· sqlite3_uri_int64()
· The PRAGMA cache_size statement has been enhanced. Formerly, you would use this statement to tell SQLite how many pages of the database files it should hold in its cache at once. The total memory requirement would depend on the database page size. Now, if you give PRAGMA cache_size a negative value -N, it will allocate roughly N kibibytes of memory to cache, divided up according to page size. This enhancement allows programs to more easily control their memory usage
· There have been several obscure bug fixes. One noteworthy bug, ticket ff5be73dee, could in theory result in a corrupt database file if a power loss occurred at just the wrong moment on an unusually cantankerous disk drive. But that is mostly a theoretical concern and is very unlikely to happen in practice. The bug was found during laboratory testing and has never been observed to occur in the wild
November 1st, 2011· If a search token (on the right-hand side of the MATCH operator) in FTS4 begins with "^" then that token must be the first in its field of the document.
· Added options SQLITE_DBSTATUS_CACHE_HIT and SQLITE_DBSTATUS_CACHE_MISS to the sqlite3_db_status() interface.
· Removed support for SQLITE_ENABLE_STAT2, replacing it with the much more capable SQLITE_ENABLE_STAT3 option.
· Enhancements to the sqlite3_analyzer utility program, including the --pageinfo and --stats options and support for multiplexed databases.
· Enhance the sqlite3_data_count() interface so that it can be used to determine if SQLITE_DONE has been seen on the prepared statement.
· Added the SQLITE_FCNTL_OVERWRITE file-control by which the SQLite core indicates to the VFS that the current transaction will overwrite the entire database file.
· Increase the default lookaside memory allocator allocation size from 100 to 128 bytes.
· Enhanced the query planner so that it can factor terms in and out of OR expressions in the WHERE clause in an effort to find better indices.
· Added the SQLITE_DIRECT_OVERFLOW_READ compile-time option, causing overflow pages to be read directly from the database file, bypassing the page cache.
· Remove limits on the magnitude of precision and width value in the format specifiers of the sqlite3_mprintf() family of string rendering routines.
· Fix a bug that prevent ALTER TABLE ... RENAME from working on some virtual tables in a database with a UTF16 encoding.
· Fix a bug in ASCII-to-float conversion that causes slow performance and incorrect results when converting numbers with ridiculously large exponents.
· Fix a bug that causes incorrect results in aggregate queries that use multiple aggregate functions whose arguments contain complicated expressions that differ only in the case of string literals contained within those expressions.
· Fix a bug that prevented the page_count and quick_check pragmas from working correctly if their names were capitalized.
· Fix a bug that caused VACUUM to fail if the count_changes pragma was engaged.
· Fix a bug in virtual table implementation that causes a crash if an FTS4 table is dropped inside a transaction and a SAVEPOINT occurs afterwards.
September 20th, 2011· This release features a new "external merge sort" algorithm used to implement ORDER BY and GROUP BY and also to presort the content of an index for CREATE INDEX. The new algorithm does approximately the same number of comparisons and I/Os as before, but the I/Os are much more sequential and so runtimes are greatly reduced when the size of the set being sorted is larger than the filesystem cache. The performance improvement can be dramatic - orders of magnitude faster for large CREATE INDEX commands. On the other hand, the code is slightly slower (1% or 2%) for a small CREATE INDEX. Since CREATE INDEX is not an operation that commonly occurs on a speed-critical path, we feel that this tradeoff is a good one. The slight slowdown for small CREATE INDEX statements might be recovered in a future release. ORDER BY and GROUP BY operations should now be faster for all cases, large and small.
· The query planner has been enhanced to do a better job of handling the DISTINCT keyword on SELECT statements.
· There has been a lot of work on the default VFSes. The unix VFS has been enhanced to include more overrideable system calls - a feature requested by Chromium to make it easier to build SQLite into a sandbox. The windows VFS has been enhanced to be more resistant to interference from anti-virus software.
June 24th, 2011· Add support for URI filenames
· Add the sqlite3_vtab_config() interface in support of ON CONFLICT clauses with virtual tables.
· Add the xSavepoint, xRelease and xRollbackTo methods in virtual tables in support of SAVEPOINT for virtual tables.
· Update the built-in FTS3/FTS4 and RTREE virtual tables to support ON CONFLICT clauses and REPLACE.
· Avoid unnecessary reparsing of the database schema.
· Added support for the FTS4 prefix option and the FTS4 order option.
· Allow WAL-mode databases to be opened read-only as long as there is an existing read/write connection.
· Added support for short filenames.
Find us on Google+
