Path to this page:
Subject: CVS commit: pkgsrc
From: Adam Ciarcinski
Date: 2018-09-17 18:14:07
Message id: 20180917161407.9B1B9FBF8@cvs.NetBSD.org
Log Message:
sqlite3: updated to 3.25.0
SQLite Release 3.25.0:
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 command-line shell.
Added the SQLITE_FCNTL_DATA_VERSION file-control.
Added the Geopoly module
Bug fixes:
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.
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.
Files: