Small. Fast. Reliable.
Choose any three.

## SQLite Release 3.25.2 On 2018-09-25

1. Add the PRAGMA legacy_alter_table=ON command that causes the "ALTER TABLE RENAME" command to behave as it did in SQLite versions 3.24.0 and earlier: references to the renamed table inside the bodies of triggers and views are not updated. This new pragma provides a compatibility work around for older programs that expected the older, wonky behavior of ALTER TABLE RENAME.
2. Fix a problem with the new window functions implementation that caused a malfunction when complicated expressions involving window functions were used inside of a view.
3. Fixes for various other compiler warnings and minor problems associated with obscure configurations.

   Hashes:

4. SQLITE_SOURCE_ID: "2018-09-25 19:08:10 fb90e7189ae6d62e77ba3a308ca5d683f90bbe633cf681865365b8e92792d1c7"
5. SHA3-256 for sqlite3.c: 34c23ff91631ae10354f8c9d62fd7d65732b3d7f3acfd0bbae31ff4a62fe28af

Changes carried forward from version 3.25.1 (2018-09-18):

1. 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. Ticket b41031ea2b537237.
2. 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 510cde277783b5fb

Changes carried forward from version 3.25.0 (2018-09-15):

1. Add support for window functions
2. Enhancements the ALTER TABLE command:
   1. Add support for renaming columns within a table using ALTER TABLE table RENAME COLUMN oldname TO newname.
   2. Fix table rename feature so that it also updates references to the renamed table in triggers and views.
3. Query optimizer improvements:
   1. 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.
   2. 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.
   3. 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".
4. 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.
5. Enhance the PRAGMA integrity_check command for improved detection of problems on the page freelist.
6. Output infinity as 1e999 in the ".dump" command of the command-line shell.
7. Added the SQLITE_FCNTL_DATA_VERSION file-control.
8. Added the Geopoly module

   Bug fixes:

9. The ORDER BY LIMIT optimization might have caused an infinite loop in the byte code of the prepared statement under very obscure circumstances, due to a confluence of minor defects in the query optimizer. Fix for ticket 9936b2fa443fec03ff25
10. 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 79cad5e4b2e219dd197242e9e.
11. 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 7be932dfa60a8a6b3b26bcf76.
12. 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 c94369cae9b561b1f996d0054b

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.