After the SQLite community, last month, released a draft of what users can expect in the SQLite’s next release, the community finally announced the release of SQLite 3.25.0 yesterday.
The primary update, however, is that they have added a support for windows functions and have provided improvements in the query optimizer.
Let’s have a closer look at what the new features in this version are.
Features in SQLite 3.25.0
- A support for windows functions has been added in this SQLite release
- The ALTER TABLE command has been enhanced with
- Improvements to the Query Optimizer include:
- 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”.
- Users now have 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.
- The PRAGMA integrity_check command has been enhanced for improved detection of problems on the page freelist.
- This version showcases the infinity output as 1e999 in the “.dump” command of the command-line shell.
- A SQLITE_FCNTL_DATA_VERSION file-control has been added.
- A Geopoly module has been added.
Bug fixes in SQLite 3.25.0
The August draft release had showcased fixes for two tickets. However, the final release has four ticket fixes including,
Fix for ORDER BY LIMIT optimization
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.
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 “.stats on” command
Avoid using a prepared statement for “.stats on” command of the CLI after it has been closed by the “.eqp full” logicc.
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.
For more details, visit SQLite 3.25.0 release log.