|
|
SQLite version 3.6.2 contains rewrites of the page-cache subsystem and the procedures for matching identifiers to table columns in SQL statements. These changes are designed to better modularize the code and make it more maintainable and reliable moving forward. Nearly 5000 non-comment lines of core code (about 11.3%) have changed from the previous release. Nevertheless, there should be no application-visible changes, other than bug fixes.
SQLite version 3.6.1 is a stabilization and performance enhancement release.
Version 3.6.0 makes changes to the VFS object in order to make SQLite more easily portable to a wider variety of platforms. There are potential incompatibilities with some legacy applications. See the 35to36.html document for details.
Many new interfaces are introduced in version 3.6.0. The code is very well tested and is appropriate for use in stable systems. We have attached the "beta" designation only so that we can make tweaks to the new interfaces in the next release without having to declare an incompatibility.
Version 3.5.9 adds a new experimental PRAGMA: journal_mode. Setting the journal mode to PERSIST can provide performance improvement on systems where deleting a file is expective. The PERSIST journal mode is still considered experimental and should be used with caution pending further testing.
Version 3.5.9 is intended to be the last stable release prior to version 3.6.0. Version 3.6.0 will make incompatible changes to the sqlite3_vfs VFS layer in order to address deficiencies in the original design. These incompatibilities will only effect programmers who write their own custom VFS layers (typically embedded device builders). The planned VFS changes will be much smaller than the changes that occurred on the 3.4.2 to 3.5.0 transaction that occurred last September.
This release of SQLite is considered stable and ready for production use.
Version 3.5.8 includes some important new performance optimizations in the virtual machine code generator, including constant subexpression factoring and common subexpression elimination. This release also creates new public interfaces: sqlite3_randomness() provides access to SQLite's internal pseudo-random number generator, sqlite3_limit() allows size limits to be set at run-time on a per-connection basis, and sqlite3_context_db_handle() is a convenience routine that allows an application-defined SQL function implementation to retrieve its database connection handle.
This release of SQLite is considered stable and ready for production use.