Small. Fast. Reliable.
Choose any three.
SQLite Release 3.25.1 On 2018-09-18
Prior changes from version 3.25.0 (2018-09-15):
- Add support for window functions
- Enhancements the ALTER TABLE command:
- Add support for renaming columns within a table using
ALTER TABLE table RENAME COLUMN oldname TO newname.
- Fix table rename feature so that it also updates references
to the renamed table in triggers and views.
- Query optimizer improvements:
- Avoid unnecessary loads of columns in an aggregate query that
are not within an aggregate function and that are not part
of the GROUP BY clause.
- The IN-early-out optimization: When doing a look-up on a
multi-column index and an IN operator is used on a column
other than the left-most column, then if no rows match against
the first IN value, check to make sure there exist rows that
match the columns to the right before continuing with the
next IN value.
- Use the transitive property to try to propagate constant
values within the WHERE clause. For example, convert
"a=99 AND b=a" into "a=99 AND b=99".
- Use a separate mutex on every inode in the unix VFS, rather than
a single mutex shared among them all, for slightly better concurrency
in multi-threaded environments.
- Enhance the PRAGMA integrity_check command for improved detection
of problems on the page freelist.
- Output infinity as 1e999 in the ".dump" command of the
- Added the SQLITE_FCNTL_DATA_VERSION file-control.
- Added the Geopoly module
- The ORDER BY LIMIT optimization might have caused an infinite loop
in the byte code of the prepared statement under very obscure
due to a confluence of minor defects in the query optimizer.
Fix for ticket
- On an UPSERT when the order of constraint checks is rearranged,
ensure that the affinity transformations on the inserted content
occur before any of the constraint checks. Fix for ticket
- Avoid using a prepared statement for ".stats on" command of the
CLI after it has been closed by the ".eqp full" logicc. Fix for ticket
- The LIKE optimization was generating incorrect byte-code and hence
getting the wrong answer
if the left-hand operand has numeric affinity and the right-hand-side
pattern is '/%' or if the pattern begins with the ESCAPE character.
Fix for ticket
Changes in this specific patch release, version 3.25.1 (2018-09-18):
- Extra sanity checking added to ALTER TABLE in the 3.25.0 release
sometimes raises a false-positive
when the table being modified has a trigger that
updates a virtual table. The false-positive caused the ALTER
TABLE to rollback, thus leaving the schema unchanged.
- The fix in the 3.25.0 release for the endless-loop in the byte-code
associated with the ORDER BY LIMIT optimization did not work for
some queries involving window functions. An additional correction
is required. Ticket
- SQLITE_SOURCE_ID: "2018-09-18 20:20:44 2ac9003de44da7dafa3fbb1915ac5725a9275c86bf2f3b7aa19321bf1460b386"
- SHA3-256 for sqlite3.c: 1b2302e7a54cc99c84ff699a299f61f069a28e1ed090b89e4430ca80ae2aab06
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.