Release Notes: This release fixes a bug that could cause database corruption when a multi-processor system attempted to rollback an incomplete transaction following a system crash. It also fixes various other less severe bugs and enhances the query optimizer.
Release Notes: A bug was fixed that might cause database corruption if a VACUUM failed and rolled back while processing a file larger than 1GiB. Optimizer improvements were made and support for COUNT(DISTINCT) was added.
Release Notes: A bug in the VACUUM command that can sometimes cause database corruption has been fixed. This bug has been present in all prior releases of SQLite that supported VACUUM, but because it is rarely hit, it was only recently noticed. It is recommended that all users upgrade. This is also (by coincidence) the first stable release of the 3.1 branch. The new capabilities include correlated subqueries, autovacuum, autoincrement, ALTER TABLE, and more.
Release Notes: A bug in the VACUUM command that can, in rare cases, lead to database corruption has been fixed. Other minor fixes that have been accumulating in the CVS repository are also included in this release.
Release Notes: A bug has been fixed that could cause index corruption if a large negative number (less than -2147483648) was inserted into an indexed numeric column.
Release Notes: A bug that might cause database corruption has been fixed. The bug is obscure and difficult to trigger, but because of the severe consequences, users are advised to upgrade.
Release Notes: A design flaw in the structure of indices was fixed.
Release Notes: A bug was fixed that could (rarely) cause database corruption during a rollback. Users of versions 2.4.0 through 2.5.4 should upgrade.
Release Notes: A bug that could potentially cause database corruption was fixed. Users of versions 2.4.0 through 2.5.2 are advised to upgrade.
Release Notes: A bug that prevented the IN operator from working correctly if either operand was derived from an INTEGER PRIMARY KEY column was fixed.