![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / devel / lemon
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
sqlite3: updated to 3.47.2 version 3.47.2 (2024-12-07): Fix a problem in text-to-floating-point conversion for SQLite that can cause values between '1.8446744073709550592eNNN' and '1.8446744073709551609eNNN' for any exponent NNN to be rendered incorrectly. In other words, some numeric text values where the first 16 significant digits are '1844674407370955' might be converted into the wrong floating-point value. See forum thread 569a7209179a7f5e. This problem only arises on x64 and i386 hardware. The problem was introduced in 3.47.0. Other minor bug fixes.
sqlite3: updated to 3.47.1 3.47.1 (2024-11-25): Fix the makefiles so that they once again honored DESTDIR for the "install" target. Add the SQLITE_IOCAP_SUBPAGE_READ capability to the VFS, to work around issues on some non-standard VFSes caused by making SQLITE_DIRECT_OVERFLOW_READ the default in version 3.45.0. Fix problems with line endings in the new sqlite3_rsync.exe utility on Windows. Fix incorrect answers to certain obscure IN queries caused by new query optimizations added in the 3.47.0 release. Other minor bug fixes.
sqlite3: updated to 3.47.0 SQLite Release 3.47.0 Allow arbitrary expressions in the second argument to the RAISE function. If the RHS of the ->> operator is negative, then access array elements counting from the right. Fix a problem with rolling back hot journal files in the seldom-used unix-dotfile VFS. FTS5 tables can now be dropped even if they use a non-standard tokenizer that has not been registered. Fix the group_concat() aggregate function so that it returns an empty string, not a NULL, if it receives a single input value which is an empty string. Enhance the generate_series() table-valued function so that it is able to recognize and use constraints on its output value. Preupdate hooks now recognize when a column added by ALTER TABLE ADD COLUMN has a non-null default value. Performance optimizations: Improved reuse of subqueries associated with the IN operator, especially when the IN operator has been duplicated due to predicate push-down. Use a Bloom filter on subqueries on the right-hand side of the IN operator, in cases where that seems likely to improve performance. Ensure that queries like "SELECT func(a) FROM tab GROUP BY 1" only invoke the func() function once per row. No attempt is made to create automatic indexes on a column that is known to be non-selective because of its use in other indexes that have been analyzed. Adjustments to the query planner so that it produces better plans for star queries with a large number of dimension tables. Add the "order-by-subquery" optimization, that seeks to disable sort operations in outer queries if the desired order is obtained naturally due to ORDER BY clauses in subqueries. The "indexed-subtype-expr" optimization strives to use expressions that are part of an index rather than recomputing the expression based on table values, as long as the query planner can prove that the subtype of the expression will never be used. Miscellaneous coding tweaks for faster runtimes. Enhancements to SQLite-related command-line programs: Add the experimental sqlite3_rsync program. Add extension functions median(), percentile(), percentile_cont(), and percentile_disc() to the CLI. Add the .www dot-command to the CLI. The sqlite3_analyzer utility now provides a break-out of statistics for WITHOUT ROWID tables. The sqldiff utility avoids creating an empty database if its second argument does not exist. Enhance the sqlite_dbpage table-valued function such that INSERT can be used to increase or decrease the size of the database file. SQLite no longer makes any use of the "long double" data type, as hardware support for long double is becoming less common and long double creates challenges for some compiler tool chains. Instead, SQLite uses Dekker's algorithm when extended precision is needed. The TCL Interface for SQLite supports TCL9. Everything probably still works for TCL 8.5 and later, though this is not guaranteed. Users are encouraged to upgrade to TCL9. JavaScript/WASM: Fix a corruption-causing bug in the JavaScript "opfs" VFS. Correct "mode=ro" handling for the "opfs" VFS. Work around a couple of browser-specific OPFS quirks. FTS5 Changes: Add the fts5_tokenizer_v2 API and the locale=1 option, for creating custom locale-aware tokenizers and fts5 tables that may take advantage of them. Add the contentless_unindexed=1 option, for creating contentless fts5 tables that store the values of any UNINDEXED columns persistently in the database. Allow an FTS5 table to be dropped even if it uses a custom tokenizer whose implementation is not available.
sqlite3: updated to 3.46.1 3.46.1 (2024-08-13): Improved robustness while parsing the tokenize= arguments in FTS5. Forum post 171bcc2bcd. Enhancements to covering index prediction in the query planner. Add early detection of over-prediction of covering indexes so that sqlite3_prepare() will return an error rather than just generate bad bytecode. Forum post e60e4c295d22f8ce. Do not let the number of terms on a VALUES clause be limited by SQLITE_LIMIT_COMPOUND_SELECT, even if the VALUES clause contains elements that appear to be variables due to double-quoted string literals. Fix the window function version of group_concat() so that it returns an empty string if it has one or more empty string inputs. In FTS5 secure-delete mode, fix false-positive integrity-check reports about corrupt indexes. Syntax errors in ALTER TABLE should always return SQLITE_ERROR. In some cases, they were formerly returning SQLITE_INTERNAL. JavaScript/WASM: Fix a corruption-causing bug in the JavaScript "opfs" VFS. Work around a couple of browser-specific OPFS quirks. Other minor fixes.
sqlite3: updated to 3.46.0
SQLite Release 3.46.0 On 2024-05-23
Enhance PRAGMA optimize in multiple ways, to make it simpler to use:
PRAGMA optimize automatically implements a temporary analysis limit to prevent excess runtime on large databases.
Added the new 0x10000 bitmask option to check for updates on all tables.
Automatically re-analyze tables that do not have sqlite_stat1 entries.
Enhancements to the date and time functions:
The strftime() SQL function now supports %G, %g, %U, and %V.
New modifiers 'ceiling' and 'floor' control the algorithm used to resolve ambiguous dates when shifting a date by an integer number of months and/or years.
The 'utc' and 'localtime' modifiers are now no-ops if SQLite knows that the time is already in UTC or in the localtime, respectively.
Add support for underscore ("_") characters between digits in numeric literals.
Add the json_pretty() SQL function.
Query planner improvements:
The "VALUES-as-coroutine" optimization enables INSERT statements with thousands of rows in the VALUES clause to parse and run in about half the time and using about half as much memory.
Allow the use of an index for queries like "SELECT count(DISTINCT col) FROM ...", even if the index records are not smaller than the table records.
Improved recognition of cases where the value of an SQL function is constant because all its arguments are constant.
Enhance the WHERE-clause push-down optimization so that it is able to push down WHERE clause terms containing uncorrelated subqueries.
Allocate additional memory from the heap for the SQL parser stack if that stack overflows, rather than reporting a "parser stack overflow" error.
JSON changes:
Allow ASCII control characters within JSON5 string literals.
Fix the -> and ->> operators so that when the right-hand side operand is a string that looks like an integer it is still treated as a string, because that is what PostgreSQL does.
Allow large hexadecimal literals to be used as the DEFAULT value to a table column.
sqlite3: updated to 3.45.3 3.45.3 (2024-04-15): Fix a long-standing bug (going back to version 3.24.0) that might (rarely) cause the "old.*" values of an UPDATE trigger to be incorrect if that trigger fires in response to an UPSERT. Forum post 284955a3cd454a15. Fix a bug in sum() that could cause it to return NULL when it should return Infinity. Forum post 23b8688ef4. Other trifling corrections and compiler warning fixes that have come up since the previous patch release. See the timeline for details.
sqlite3: updated to 3.45.2 version 3.45.2 (2024-03-12): Fix an error in UPSERT, introduced by enhancement 3a in version 3.35.0 (2021-03-12), that could cause an index to get out-of-sync with its table. Forum thread 919c6579c8. Reduce the scope of the NOT NULL strength reduction optimization that was added as item 8e in version 3.35.0 (2021-03-12). The optimization was being attempted in some contexts where it did not work, resulting in incorrect query results. Forum thread 440f2a2f17. Other trifling corrections and compiler warning fixes that have come up since the previous patch release. See the timeline for details.
sqlite3* lemon: updated to 3.45.1 version 3.45.1 (2024-01-30): Restore the JSON BLOB input bug, and promise to support the anomaly in subsequent releases, for backward compatibility. Fix the PRAGMA integrity_check command so that it works on read-only databases that contain FTS3 and FTS5 tables. This resolves an issue introduced in version 3.44.0 but was undiscovered until after the 3.45.0 release. Fix issues associated with processing corrupt JSONB inputs: Prevent exponential runtime when converting a corrupt JSONB into text. Fix a possible read of one byte past the end of the JSONB blob when converting a corrupt JSONB into text. Enhanced testing using jfuzz to prevent any future JSONB problems such as the above. Fix a long-standing bug in which a read of a few bytes past the end of a memory-mapped segment might occur when accessing a craftily corrupted database using memory-mapped database. Fix a long-standing bug in which a NULL pointer dereference might occur in the bytecode engine due to incorrect bytecode being generated for a class of SQL statements that are deliberately designed to stress the query planner but which are otherwise pointless.
sqlite3: updated to 3.45.0 SQLite Release 3.45.0 On 2024-01-15 Added the SQLITE_RESULT_SUBTYPE property for application-defined SQL functions. All application defined SQL functions that invokes sqlite3_result_subtype() must be registered with this new property. Failure to do so might cause the call to sqlite3_result_subtype() to behave as a no-op. Compile with -DSQLITE_STRICT_SUBTYPE=1 to cause an SQL error to be raised if a function that is not SQLITE_RESULT_SUBTYPE tries invokes sqlite3_result_subtype(). The use of -DSQLITE_STRICT_SUBTYPE=1 is a recommended compile-time option for every application that makes use of subtypes. Enhancements to the JSON SQL functions: All JSON functions are rewritten to use a new internal parse tree format called JSONB. The new parse-tree format is serializable and hence can be stored in the database to avoid unnecessary re-parsing whenever the JSON value is used. New versions of JSON-generating functions generate binary JSONB instead of JSON text. The json_valid() function adds an optional second argument that specifies what it means for the first argument to be "well-formed". Add the FTS5 tokendata option to the FTS5 virtual table. The SQLITE_DIRECT_OVERFLOW_READ optimization is now enabled by default. Disable it at compile-time using -DSQLITE_DIRECT_OVERFLOW_READ=0. Query planner improvements: Do not allow the transitive constraint optimization to trick the query planner into using a range constraint when a better equality constraint is available. (Forum post 2568d1f6e6.) The query planner now does a better job of disregarding indexes that ANALYZE identifies as low-quality. (Forum post 6f0958b03b.) Increase the default value for SQLITE_MAX_PAGE_COUNT from 1073741824 to 4294967294. Enhancements to the CLI: Improvements to the display of UTF-8 content on Windows Automatically detect playback of ".dump" scripts and make appropriate changes to settings such as ".dbconfig defensive off" and ".dbconfig dqs_dll on".
sqlite3: updated to 3.44.2 3.44.1 (2023-11-22): Change the CLI so that it uses UTF-16 for console I/O on Windows. This enables proper display of unicode text on old Windows7 machines. Other obscure bug fixes. 3.44.2 (2023-11-24): Fix a mistake in the CLI that was introduced by the fix (item 15 above) in 3.44.1. Fix a problem in FTS5 that was discovered during internal fuzz testing only minutes after the 3.44.1 release was tagged. Fix incomplete assert() statements that the fuzzer discovered the day after the previous release. Fix a couple of harmless compiler warnings that appeared in debug builds with GCC 16.
sqlite3: updated to 3.44.0 SQLite Release 3.44.0 On 2023-11-01 Aggregate functions can now include an ORDER BY clause after their last parameter. The arguments to the function are processed in the order specified. This can be important for functions like string_agg() and json_group_array(). Add support for the concat() and concat_ws() scalar SQL functions, compatible with PostgreSQL, SQLServer, and MySQL. Add support for the string_agg() aggregate SQL function, compatible with PostgreSQL and SQLServer. New conversion letters on the strftime() SQL function: %e %F %I %k %l %p %P %R %T %u Add new C-language APIs: sqlite3_get_clientdata() and sqlite3_set_clientdata(). Many errors associated with CREATE TABLE are now raised when the CREATE TABLE statement itself is run, rather than being deferred until the first time the table is actually used. The PRAGMA integrity_check command now verifies the consistency of the content in various built-in virtual tables using the new xIntegrity method. This works for the FTS3, FTS4, FTS5, RTREE, and GEOPOLY extensions. The SQLITE_DBCONFIG_DEFENSIVE setting now prevents PRAGMA writable_schema from being turned on. Previously writable_schema could be turned on, but would not actually allow the schema to be writable. Now it simply cannot be turned on. Tag the built-in FTS3, FTS4, FTS5, RTREE, and GEOPOLY virtual tables as SQLITE_VTAB_INNOCUOUS so that they can be used inside of triggers in high-security deployments. The PRAGMA case_sensitive_like statement is deprecated, as its use when the schema contains LIKE operators can lead to reports of database corruption by PRAGMA integrity_check. SQLITE_USE_SEH (Structured Exception Handling) is now enabled by default whenever SQLite is built using the Microsoft C compiler. It can be disabled using -DSQLITE_USE_SEH=0 Query planner optimizations: In partial index scans, if the WHERE clause implies a constant value for a table column, replace occurrences of that table column with the constant. This increases the likelihood of the partial index being a covering index. Disable the view-scan optimization (added in version 3.42.0 - item 1c) as it was causing multiple performance regressions. In its place, reduce the estimated row count for DISTINCT subqueries by a factor of 8. SQLite now performs run-time detection of whether or not the underlying hardware supports "long double" with precision greater than "double" and uses appropriate floating-point routines depending on what it discovered. The CLI for Windows now defaults to using UTF-8 for both input and output on platforms that support it. The --no-utf8 option is available to disable UTF8 support.
sqlite3: updated to 3.43.2 Changes in this specific patch release, version 3.43.2 (2023-10-10): Fix a couple of obscure UAF errors and an obscure memory leak. Omit the use of the sprintf() function from the standard library in the CLI, as this now generates warnings on some platforms. Avoid conversion of a double into unsigned long long integer, as some platforms do not do such conversions correctly.
sqlite3: updated to 3.43.1 3.43.1 Fix a regression in the way that the sum(), avg(), and total() aggregate functions handle infinities. Fix a bug in the json_array_length() function that occurs when the argument comes directly from json_remove(). Fix the omit-unused-subquery-columns optimization (introduced in in version 3.42.0) so that it works correctly if the subquery is a compound where one arm is DISTINCT and the other is not. Other minor fixes.
databases/sqlite3* devel/lemon: updated to 2.43.0 SQLite Release 3.43.0 On 2023-08-24 Add support for Contentless-Delete FTS5 Indexes. This is a variety of FTS5 full-text search index that omits storing the content that is being indexed while also allowing records to be deleted. Enhancements to the date and time functions: Added new time shift modifiers of the form ±YYYY-MM-DD HH:MM:SS.SSS. Added the timediff() SQL function. Added the octet_length(X) SQL function. Added the sqlite3_stmt_explain() API. Query planner enhancements: Generalize the LEFT JOIN strength reduction optimization so that it works for RIGHT and FULL JOINs as well. Rename it to OUTER JOIN strength reduction. Enhance the theorem prover in the OUTER JOIN strength reduction optimization so that it returns fewer false-negatives. Enhancements to the decimal extension: New function decimal_pow2(N) returns the N-th power of 2 for integer N between -20000 and +20000. New function decimal_exp(X) works like decimal(X) except that it returns the result in exponential notation - with a "e+NN" at the end. If X is a floating-point value, then the decimal(X) function now does a full expansion of that value into its exact decimal equivalent. Performance enhancements to JSON processing results in a 2x performance improvement for some kinds of processing on large JSON strings. New makefile target "verify-source" checks to ensure that there are no unintentional changes in the source tree. (Works for canonical source code only - not for precompiled amalgamation tarballs.) Added the SQLITE_USE_SEH compile-time option that enables Structured Exception Handling on Windows while working with the memory-mapped shm file that is part of WAL mode processing. This option is enabled by default when building on Windows using Makefile.msc. The VFS for unix now assumes that the nanosleep() system call is available unless compiled with -DHAVE_NANOSLEEP=0.
sqlite3: updated to 3.42.0 SQLite Release 3.42.0 On 2023-05-16 Add the FTS5 secure-delete command. This option causes all forensic traces to be removed from the FTS5 inverted index when content is deleted. Enhance the JSON SQL functions to support JSON5 extensions. The SQLITE_CONFIG_LOG and SQLITE_CONFIG_PCACHE_HDRSZ calls to sqlite3_config() are now allowed to occur after sqlite3_initialize(). New sqlite3_db_config() options: SQLITE_DBCONFIG_STMT_SCANSTATUS and SQLITE_DBCONFIG_REVERSE_SCANORDER. Query planner improvements: Enable the "count-of-view" optimization by default. Avoid computing unused columns in subqueries. Improvements to the push-down optimization. Enhancements to the CLI: Add the --unsafe-testing command-line option. Without this option, some dot-commands (ex: ".testctrl") are now disabled because those commands that are intended for testing only and can cause malfunctions misused. Allow commands ".log on" and ".log off", even in --safe mode. "--" as a command-line argument means all subsequent arguments that start with "-" are interpreted as normal non-option argument. Magic parameters ":inf" and ":nan" bind to floating point literals Infinity and NaN, respectively. The --utf8 command-line option omits all translation to or from MBCS on the Windows console for interactive sessions, and sets the console code page for UTF-8 I/O during such sessions. The --utf8 option is a no-op on all other platforms. Add the ability for application-defined SQL functions to have the same name as join keywords: CROSS, FULL, INNER, LEFT, NATURAL, OUTER, or RIGHT. Enhancements to PRAGMA integrity_check: Detect and raise an error when a NaN value is stored in a NOT NULL column. Improved error message output identifies the root page of a b-tree when an error is found within a b-tree. Allow the session extension to be configured to capture changes from tables that lack an explicit ROWID. Added the subsecond modifier to the date and time functions. Negative values passed into sqlite3_sleep() are henceforth interpreted as 0. The maximum recursion depth for JSON arrays and objects is lowered from 2000 to 1000. Extended the built-in printf() function so the comma option now works with floating-point conversions in addition to integer conversions. Miscellaneous bug fixes and performance optimizations
sqlite3: updated to 3.41.2 version 3.41.2 (2023-03-22): Multiple fixes for reads past the end of memory buffers (NB: reads not writes) in the following circumstances: When processing a corrupt database file using the non-standard SQLITE_ENABLE_STAT4 compile-time option. In the CLI when the sqlite3_error_offset() routine returns an out-of-range value (see also the fix to sqlite3_error_offset() below). In the recovery extension. In FTS3 when processing a corrupt database file. Fix the sqlite3_error_offset() so that it does not return out-of-range values when reporting errors associated with generated columns. Multiple fixes in the query optimizer for problems that cause incorrect results for bizarre, fuzzer-generated queries. Increase the size of the reference counter in the page cache object to 64 bits to ensure that the counter never overflows. Fix a performance regression caused by a bug fix in patch release 3.41.1. Fix a few incorrect assert() statements.
sqlite3: updated to 3.41.1 version 3.41.1 (2023-03-10): Provide compile-time options -DHAVE_LOG2=0 and -DHAVE_LOG10=0 to enable SQLite to be compiled on systems that omit the standard library functions log2() and log10(), repectively. Ensure that the datatype for column t1.x in "CREATE TABLE t1 AS SELECT CAST(7 AS INT) AS x;" continues to be INT and is not NUM, for historical compatibility. Enhance PRAGMA integrity_check to detect when extra bytes appear at the end of an index record. Fix various obscure bugs reported by the user community. See the timeline of changes for details.
sqlite3: updated to 3.41.0 SQLite Release 3.41.0 On 2023-02-21 Query planner improvements: Make use of indexed expressions within an aggregate query that includes a GROUP BY clause. The query planner has improved awareness of when an index is a covering index and adjusts predicted runtimes accordingly. The query planner is more aggressive about using co-routines rather than materializing subqueries and views. Queries against the built-in table-valued functions json_tree() and json_each() will now usually treat "ORDER BY rowid" as a no-op. Enhance the ability of the query planner to use indexed expressions even if the expression has been modified by the constant-propagation optimization. (See forum thread 0a539c7.) Add the built-in unhex() SQL function. Add the base64 and base85 application-defined functions as an extension and include that extension in the CLI. Add the sqlite3_stmt_scanstatus_v2() interface. (This interface is only available if SQLite is compiled using SQLITE_ENABLE_STMT_SCANSTATUS.) In-memory databases created using sqlite3_deserialize() now report their filename as an empty string, not as 'x'. Changes to the CLI: Add the new base64() and base85() SQL functions Enhanced EXPLAIN QUERY PLAN output using the new sqlite3_stmt_scanstatus_v2() interface when compiled using SQLITE_ENABLE_STMT_SCANSTATUS. The ".scanstats est" command provides query planner estimates in profiles. The continuation prompt indicates if the input is currently inside of a string literal, identifier literal, comment, trigger definition, etc. Enhance the --safe command-line option to disallow dangerous SQL functions. The double-quoted string misfeature is now disabled by default for CLI builds. Legacy use cases can reenable the misfeature at run-time using the ".dbconfig dqs_dml on" and ".dbconfig dqs_ddl on" commands. Enhance the PRAGMA integrity_check command so that it detects when text strings in a table are equivalent to but not byte-for-byte identical to the same strings in the index. Enhance the carray table-valued function so that it is able to bind an array of BLOB objects. Added the sqlite3_is_interrupted() interface. Long-running calls to sqlite3_prepare() and similar now invoke the progress handler callback and react to sqlite3_interrupt(). The sqlite3_vtab_in_first() and sqlite3_vtab_in_next() functions are enhanced so that they reliably detect if they are invoked on a parameter that was not selected for multi-value IN processing using sqlite3_vtab_in(). They return SQLITE_ERROR instead of SQLITE_MISUSE in this case. The parser now ignores excess parentheses around a subquery on the right-hand side of an IN operator, so that SQLite now works the same as PostgreSQL in this regard. Formerly, SQLite treated the subquery as an expression with an implied "LIMIT 1". Added the SQLITE_FCNTL_RESET_CACHE option to the sqlite3_file_control() API. Makefile improvements: The new makefile target "sqlite3r.c" builds an amalgamation that includes the recovery extension. New makefile targets "devtest" and "releasetest" for running a quick developmental test prior to doing a check-in and for doing a full release test, respectively. Miscellaneous performance enhancements.
sqlite3: updated to 3.40.1 3.40.1 (2022-12-28): Fix the --safe command-line option to the CLI such that it correctly disallows the use of SQL functions like writefile() that can cause harmful side-effects. Fix a potential infinite loop in the memsys5 alternative memory allocator. This bug was introduced by a performance optimization in version 3.39.0. Various other obscure fixes.
sqlite3: updated to 3.40.0 SQLite Release 3.40.0 Add support for compiling SQLite to WASM and running it in web browsers. NB: The WASM build and its interfaces are considered "beta" and are subject to minor changes if the need arises. We anticipate finalizing the interface for the next release. Add the recovery extension that might be able to recover some content from a corrupt database file. Query planner enhancements: Recognize covering indexes on tables with more than 63 columns where columns beyond the 63rd column are used in the query and/or are referenced by the index. Extract the values of expressions contained within expression indexes where practical, rather than recomputing the expression. The NOT NULL and IS NULL operators (and their equivalents) avoid loading the content of large strings and BLOB values from disk. Avoid materializing a view on which a full scan is performed exactly once. Use and discard the rows of the view as they are computed. Allow flattening of a subquery that is the right-hand operand of a LEFT JOIN in an aggregate query. A new typedef named sqlite3_filename is added and used to represent the name of a database file. Various interfaces are modified to use the new typedef instead of "char*". This interface change should be fully backwards compatible, though it might cause (harmless) compiler warnings when rebuilding some legacy applications. Add the sqlite3_value_encoding() interface. Security enhancement: SQLITE_DBCONFIG_DEFENSIVE is augmented to prohibit changing the schema_version. The schema_version becomes read-only in defensive mode. Enhancements to the PRAGMA integrity_check statement: Columns in non-STRICT tables with TEXT affinity should not contain numeric values. Columns in non-STRICT tables with NUMERIC affinity should not contain TEXT values that could be converted into numbers. Verify that the rows of a WITHOUT ROWID table are in the correct order. Enhance the VACUUM INTO statement so that it honors they PRAGMA synchronous setting. Enhance the sqlite3_strglob() and sqlite3_strlike() APIs so that they are able to accept NULL pointers for their string parameters and still generate a sensible result. Provide the new SQLITE_MAX_ALLOCATION_SIZE compile-time option for limiting the size of memory allocations. Change the algorithm used by SQLite's built-in pseudo-random number generator (PRNG) from RC4 to Chacha20. Allow two or more indexes to have the same name as long as they are all in separate schemas. Miscellaneous performance optimizations result in about 1% fewer CPU cycles used on typical workloads.
Pullup ticket #6688 - requested by taca databases/sqlite3: security fix (for ruby-sqlite3) Revisions pulled up: - databases/sqlite3-docs/PLIST 1.118 - databases/sqlite3-docs/distinfo 1.121 - databases/sqlite3-tcl/distinfo 1.133 - databases/sqlite3/Makefile.common 1.95 - databases/sqlite3/distinfo 1.188 - devel/lemon/distinfo 1.62 --- Module Name: pkgsrc Committed By: adam Date: Mon Oct 3 12:27:52 UTC 2022 Modified Files: pkgsrc/databases/sqlite3: Makefile.common distinfo pkgsrc/databases/sqlite3-docs: PLIST distinfo pkgsrc/databases/sqlite3-tcl: distinfo pkgsrc/devel/lemon: distinfo Log Message: sqlite3: updated to 3.39.4 Changes in version 3.39.4 (2022-09-29): Fix the build on Windows so that it works with -DSQLITE_OMIT_AUTOINIT Fix a long-standing problem in the btree balancer that might, in rare cases, cause database corruption if the application uses an application-defined page cache. Enhance SQLITE_DBCONFIG_DEFENSIVE so that it disallows CREATE TRIGGER statements if one or more of the statements in the body of the trigger write into shadow tables. Fix a possible integer overflow in the size computation for a memory allocation in FTS3. Fix a misuse of the sqlite3_set_auxdata() interface in the ICU Extension.
sqlite3: updated to 3.39.4 Changes in version 3.39.4 (2022-09-29): Fix the build on Windows so that it works with -DSQLITE_OMIT_AUTOINIT Fix a long-standing problem in the btree balancer that might, in rare cases, cause database corruption if the application uses an application-defined page cache. Enhance SQLITE_DBCONFIG_DEFENSIVE so that it disallows CREATE TRIGGER statements if one or more of the statements in the body of the trigger write into shadow tables. Fix a possible integer overflow in the size computation for a memory allocation in FTS3. Fix a misuse of the sqlite3_set_auxdata() interface in the ICU Extension.
sqlite3: updated to 3.39.3 Changes in version 3.39.3 (2022-09-05): Use a statement journal on DML statement affecting two or more database rows if the statement makes use of a SQL functions that might abort. See forum thread 9b9e4716c0d7bbd1. Use a mutex to protect the PRAGMA temp_store_directory and PRAGMA data_store_directory statements, even though they are deprecated and documented as not being threadsafe. See forum post 719a11e1314d1c70. Other bug and warning fixes. See the timeline for details.
sqlite3: updated to 3.39.2 changes in version 3.39.2 (2022-07-21): Fix a performance regression in the query planner associated with rearranging the order of FROM clause terms in the presences of a LEFT JOIN. Apply fixes for CVE-2022-35737, Chromium bugs 1343348 and 1345947, forum post 3607259d3c, and other minor problems discovered by internal testing.
sqlite3: updated to 3.39.1 Changes in version 3.39.1 (2022-07-13): Fix an incorrect result from a query that uses a view that contains a compound SELECT in which only one arm contains a RIGHT JOIN and where the view is not the first FROM clause term of the query that contains the view. forum post 174afeae5734d42d. Fix some harmless compiler warnings. Fix a long-standing problem with ALTER TABLE RENAME that can only arise if the sqlite3_limit(SQLITE_LIMIT_SQL_LENGTH) is set to a very small value. Fix a long-standing problem in FTS3 that can only arise when compiled with the SQLITE_ENABLE_FTS3_PARENTHESIS compile-time option. Fix the build so that is works when the SQLITE_DEBUG and SQLITE_OMIT_WINDOWFUNC compile-time options are both provided at the same time. Fix the initial-prefix optimization for the REGEXP extension so that it works correctly even if the prefix contains characters that require a 3-byte UTF8 encoding. Enhance the sqlite_stmt virtual table so that it buffers all of its output.
sqlite3: updated to 3.39.0 SQLite Release 3.39.0 On 2022-06-25 Add (long overdue) support for RIGHT and FULL OUTER JOIN. Add new binary comparison operators IS NOT DISTINCT FROM and IS DISTINCT FROM that are equivalent to IS and IS NOT, respective, for compatibility with PostgreSQL and SQL standards. Add a new return code (value "3") from the sqlite3_vtab_distinct() interface that indicates a query that has both DISTINCT and ORDER BY clauses. Added the sqlite3_db_name() interface. The unix os interface resolves all symbolic links in database filenames to create a canonical name for the database before the file is opened. Defer materializing views until the materialization is actually needed, thus avoiding unnecessary work if the materialization turns out to never be used. The HAVING clause of a SELECT statement is now allowed on any aggregate query, even queries that do not have a GROUP BY clause. Many microoptimizations collectively reduce CPU cycles by about 2.3%.
sqlite3: updated to 3.38.5 3.38.5 (2022-05-06): Fix a blunder in the CLI of the 3.38.4 release.
sqlite3: updated to 3.38.4 3.38.4 (2022-05-04): Fix a byte-code problem in the Bloom filter pull-down optimization added by release 3.38.0 in which an error in the byte code causes the byte code engine to enter an infinite loop when the pull-down optimization encounters a NULL key.
sqlite3: updated to 3.38.3 changes in version 3.38.3 (2022-04-27): Fix a case of the query planner be overly aggressive with optimizing automatic-index and Bloom-filter construction, using inappropriate ON clause terms to restrict the size of the automatic-index or Bloom filter, and resulting in missing rows in the output. Forum thread 0d3200f4f3bcd3a3. Other minor patches. See the timeline for details.
sqlite3: updated to 3.38.2 Additional changes in version 3.38.2 (2022-03-26): Fix another user-discovered problem with the new Bloom filter optimization that might cause an incorrect answer when doing a LEFT JOIN with a WHERE clause constraint that says that one of the columns on the right table of the LEFT JOIN is NULL. See forum thread 031e262a89b6a9d2. Other minor patches. See the timeline for details.
sqlite3: updated to 3.38.1 3.38.1 (2022-03-12): Fix problems with the new Bloom filter optimization that might cause some obscure queries to get an incorrect answer. Fix the localtime modifier of the date and time functions so that it preserves fractional seconds. Fix the sqlite_offset SQL function so that it works correctly even in corner cases such as when the argument is a virtual column or the column of a view. Fix row value IN operator constraints on virtual tables so that they work correctly even if the virtual table implementation relies on bytecode to filter rows that do not satisfy the constraint. Other minor fixes to assert() statements, test cases, and documentation.
sqlite3: updated to 3.38.0 SQLite Release 3.38.0 On 2022-02-22 Added the -> and ->> operators for easier processing of JSON. The new operators are compatible with MySQL and PostgreSQL. The JSON functions are now built-ins. It is no longer necessary to use the -DSQLITE_ENABLE_JSON1 compile-time option to enable JSON support. JSON is on by default. Disable the JSON interface using the new -DSQLITE_OMIT_JSON compile-time option. Enhancements to date and time functions: Added the unixepoch() function. Added the auto modifier and the julianday modifier. Rename the printf() SQL function to format() for better compatibility. The original printf() name is retained as an alias for backwards compatibility. Added the sqlite3_error_offset() interface, which can sometimes help to localize an SQL error to a specific character in the input SQL text, so that applications can provide better error messages. Enhanced the interface to virtual tables as follows: Added the sqlite3_vtab_distinct() interface. Added the sqlite3_vtab_rhs_value() interface. Added new operator types SQLITE_INDEX_CONSTRAINT_LIMIT and SQLITE_INDEX_CONSTRAINT_OFFSET. Added the sqlite3_vtab_in() interface (and related) to enable a virtual table to process IN operator constraints all at once, rather than processing each value of the right-hand side of the IN operator separately. CLI enhancements: Columnar output modes are enhanced to correctly handle tabs and newlines embedded in text. Added options like "--wrap N", "--wordwrap on", and "--quote" to the columnar output modes. Added the .mode qbox alias. The .import command automatically disambiguates column names. Use the new sqlite3_error_offset() interface to provide better error messages. Query planner enhancements: Use a Bloom filter to speed up large analytic queries. Use a balanced merge tree to evaluate UNION or UNION ALL compound SELECT statements that have an ORDER BY clause. The ALTER TABLE statement is changed to silently ignores entries in the sqlite_schema table that do not parse when PRAGMA writable_schema=ON.
sqlite3: updated to 3.37.2 Changes in version 3.37.2: Fix a bug introduced in version 3.35.0 (2021-03-12) that can cause database corruption if a SAVEPOINT is rolled back while in PRAGMA temp_store=MEMORY mode, and other changes are made, and then the outer transaction commits. Check-in 73c2b50211d3ae26 Fix a long-standing problem with ON DELETE CASCADE and ON UPDATE CASCADE in which a cache of the bytecode used to implement the cascading change was not being reset following a local DDL change. Check-in 5232c9777fe4fb13. Other minor fixes that should not impact production builds.
sqlite3: updated to 3.37.1 version 3.37.1 Fix a bug introduced by the UPSERT enhancements of version 3.35.0 that can cause incorrect byte-code to be generated for some obscure but valid SQL, possibly resulting in a NULL-pointer dereference. Fix an OOB read that can occur in FTS5 when reading corrupt database files. Improved robustness of the --safe option in the CLI. Other minor fixes to assert() statements and test cases.
sqlite3: updated to 3.37.0
SQLite Release 3.37.0 On 2021-11-27
STRICT tables provide a prescriptive style of data type management, for developers who prefer that kind of thing.
When adding columns that contain a CHECK constraint or a generated column containing a NOT NULL constraint, the ALTER TABLE ADD COLUMN now checks new constraints against preexisting rows in the database and will only proceed if no constraints are violated.
Added the PRAGMA table_list statement.
CLI enhancements:
Add the .connection command, allowing the CLI to keep multiple database connections open at the same time.
Add the --safe command-line option that disables dot-commands and SQL statements that might cause side-effects that extend beyond the single database file named on the command-line.
Performance improvements when reading SQL statements that span many lines.
Added the sqlite3_autovacuum_pages() interface.
The sqlite3_deserialize() does not and has never worked for the TEMP database. That limitation is now noted in the documentation.
The query planner now omits ORDER BY clauses on subqueries and views if removing those clauses does not change the semantics of the query.
The generate_series table-valued function extension is modified so that the first parameter ("START") is now required. This is done as a way to demonstrate how to write table-valued functions with required parameters. The legacy behavior is available using the -DZERO_ARGUMENT_GENERATE_SERIES compile-time option.
Added new sqlite3_changes64() and sqlite3_total_changes64() interfaces.
Added the SQLITE_OPEN_EXRESCODE flag option to sqlite3_open_v2().
Use less memory to hold the database schema.
archivers: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes Could not be committed due to merge conflict: devel/py-traitlets/distinfo The following distfiles were unfetchable (note: some may be only fetched conditionally): ./devel/pvs/distinfo pvs-3.2-solaris.tgz ./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip
devel: Remove SHA1 hashes for distfiles
sqlite3: updated to 3.36.0 SQLite Release 3.36.0 On 2021-06-18 Improvement to the EXPLAIN QUERY PLAN output to make it easier to understand. Byte-order marks at the start of a token are skipped as if they were whitespace. An error is raised on any attempt to access the rowid of a VIEW or subquery. Formerly, the rowid of a VIEW would be indeterminate and often would be NULL. The -DSQLITE_ALLOW_ROWID_IN_VIEW compile-time option is available to restore the legacy behavior for applications that need it. The sqlite3_deserialize() and sqlite3_serialize() interfaces are now enabled by default. The -DSQLITE_ENABLE_DESERIALIZE compile-time option is no longer required. Instead, there is is a new -DSQLITE_OMIT_DESERIALIZE compile-time option to omit those interfaces. The "memdb" VFS now allows the same in-memory database to be shared among multiple database connections in the same process as long as the database name begins with "/". Back out the EXISTS-to-IN optimization (item 8b in the SQLite 3.35.0 change log) as it was found to slow down queries more often than speed them up. Improve the constant-propagation optimization so that it works on non-join queries. The REGEXP extension is now included in CLI builds.
sqlite3: updated to 3.35.5 version 3.35.5: Fix defects in the new ALTER TABLE DROP COLUMN feature that could corrupt the database file. Fix an obscure query optimizer problem that might cause an incorrect query result.
sqlite3: updated to 3.35.4 3.35.4 Fix a defect in the query planner optimization identified by item 8b above. Fix a defect in the new RETURNING syntax. Fix the new RETURNING feature so that it raises an error if one of the terms in the RETURNING clause references a unknown table, instead of silently ignoring that error. Fix an assertion associated with aggregate function processing that was incorrectly triggered by the push-down optimization.
sqlite3: updated to 3.35.3 changes in version 3.35.3 Enhance the OP_OpenDup opcode of the bytecode engine so that it works even if the cursor being duplicated itself came from OP_OpenDup. Fix for ticket bb8a9fd4a9b7fce5. This problem only came to light due to the recent MATERIALIZED hint enhancement. When materializing correlated common table expressions, do so separately for each use case, as that is required for correctness. This fixes a problem that was introduced by the MATERIALIZED hint enhancement. Fix a problem in the filename normalizer of the unix VFS. Fix the "box" output mode in the CLI so that it works with statements that returns one or more rows of zero columns (such as PRAGMA incremental_vacuum). Forum post afbbcb5b72. Improvements to error messages generated by faulty common table expressions. Forum post aa5a0431c99e. Fix some incorrect assert() statements. Fix to the SELECT statement syntax diagram so that the FROM clause syntax is shown correctly. Forum post 9ed02582fe. Fix the EBCDIC character classifier so that it understands newlines as whitespace. Forum post 58540ce22dcd. Improvements the xBestIndex method in the implementation of the (unsupported) wholenumber virtual table extension so that it does a better job of convincing the query planner to avoid trying to materialize a table with an infinite number of rows.
sqlite3: updated to 3.35.2 Changes in version 3.35.2: Fix a problem in the appendvfs.c extension that was introduced into version 3.35.0. Ensure that date/time functions with no arguments (which generate responses that depend on the current time) are treated as non-deterministic functions. Ticket 2c6c8689fb5f3d2f Fix a problem in the sqldiff utility program having to do with unusual whitespace characters in a virtual table definition. Limit the new UNION ALL optimization described by item 8c in the 3.35.0 release so that it does not try to make too many new subqueries. See forum thread 140a67d3d2 for details.
sqlite3: updated to 3.35.1 3.35.1: Fix a bug in the new DROP COLUMN feature when used on columns that are indexed and that are quoted in the index definition. Documentation improvements.
sqlite3: updated to 3.35.0 SQLite Release 3.35.0 On 2021-03-12 Added built-in SQL math functions(). (Requires the -DSQLITE_ENABLE_MATH_FUNCTIONS compile-time option.) Added support for ALTER TABLE DROP COLUMN. Generalize UPSERT: Allow multiple ON CONFLICT clauses that are evaluated in order, The final ON CONFLICT clause may omit the conflict target and yet still use DO UPDATE. Add support for the RETURNING clause on DELETE, INSERT, and UPDATE statements. Use less memory when running VACUUM on databases containing very large TEXT or BLOB values. It is no longer necessary to hold the entire TEXT or BLOB in memory all at once. Add support for the MATERIALIZED and NOT MATERIALIZED hints when specifying common table expressions. The default behavior was formerly NOT MATERIALIZED, but is now changed to MATERIALIZED for CTEs that are used more than once. The SQLITE_DBCONFIG_ENABLE_TRIGGER and SQLITE_DBCONFIG_ENABLE_VIEW settings are modified so that they only control triggers and views in the main database schema or in attached database schemas and not in the TEMP schema. TEMP triggers and views are always allowed. Query planner/optimizer improvements: Enhancements to the min/max optimization so that it works better with the IN operator and the OP_SeekScan optimization of the previous release. Attempt to process EXISTS operators in the WHERE clause as if they were IN operators, in cases where this is a valid transformation and seems likely to improve performance. Allow UNION ALL sub-queries to be flattened even if the parent query is a join. Use an index, if appropriate, on IS NOT NULL expressions in the WHERE clause, even if STAT4 is disabled. Expressions of the form "x IS NULL" or "x IS NOT NULL" might be converted to simply FALSE or TRUE, if "x" is a column that has a "NOT NULL" constraint and is not involved in an outer join. Avoid checking foreign key constraints on an UPDATE statement if the UPDATE does not modify any columns associated with the foreign key. Allow WHERE terms to be pushed down into sub-queries that contain window functions, as long as the WHERE term is made up of entirely of constants and copies of expressions found in the PARTITION BY clauses of all window functions in the sub-query. CLI enhancements: Enhance the ".stats" command to accept new arguments "stmt" and "vmstep", causing prepare statement statistics and only the virtual-machine step count to be shown, respectively. Add the ".filectrl data_version" command. Enhance the ".once" and ".output" commands so that if the destination argument begins with "|" (indicating that output is redirected into a pipe) then the argument does not need to be quoted. Bug fixes: Fix a potential NULL pointer dereference when processing a syntactically incorrect SELECT statement with a correlated WHERE clause and a "HAVING 0" clause. (Also fixed in the 3.34.1 patch release.) Fix a bug in the IN-operator optimization of version 3.33.0 that can cause an incorrect answer. Fix incorrect answers from the LIKE operator if the pattern ends with "%" and there is an "ESCAPE '_'" clause.
sqlite3: updated to 3.34.1 Changes in version 3.34.1: Fix a potential use-after-free bug when processing a a subquery with both a correlated WHERE clause and a "HAVING 0" clause and where the parent query is an aggregate. Fix documentation typos Fix minor problems in extensions.
sqlite3: updated to 3.34.0 SQLite Release 3.34.0 Added the sqlite3_txn_state() interface for reporting on the current transaction state of the database connection. Enhance recursive common table expressions to support two or more recursive terms as is done by SQL Server, since this helps make queries against graphs easier to write and faster to execute. Improved error messages on CHECK constraint failures. CLI enhancements: The .read dot-command now accepts a pipeline in addition to a filename. Added options --data-only and --nosys to the .dump dot-command. Added the --nosys option to the .schema dot-command. Table name quoting works correctly for the .import dot-command. The generate_series(START,END,STEP) table-valued function extension is now built into the CLI. The .databases dot-command now show the status of each database file as determined by sqlite3_db_readonly() and sqlite3_txn_state(). Added the --tabs command-line option that sets .mode tabs. The --init option reports an error if the file named as its argument cannot be opened. The --init option also now honors the --bail option. Query planner improvements: Improved estimates for the cost of running a DISTINCT operator. When doing an UPDATE or DELETE using a multi-column index where only a few of the earlier columns of the index are useful for the index lookup, postpone doing the main table seek until after all WHERE clause constraints have been evaluated, in case those constraints can be covered by unused later terms of the index, thus avoiding unnecessary main table seeks. The new OP_SeekScan opcode is used to improve performance of multi-column index look-ups when later columns are constrained by an IN operator. The BEGIN IMMEDIATE and BEGIN EXCLUSIVE commands now work even if one or more attached database files are read-only. Enhanced FTS5 to support trigram indexes. Improved performance of WAL mode locking primitives in cases where there are hundreds of connections all accessing the same database file at once. Enhanced the carray() table-valued function to include a single-argument form that is bound using the auxiliary sqlite3_carray_bind() interface. The substr() SQL function can now also be called "substring()" for compatibility with SQL Server. The syntax diagrams are now implemented as Pikchr scripts and rendered as SVG for improved legibility and ease of maintenance.
sqlite3: updated to 3.33.0 SQLite Release 3.33.0 Support for UPDATE FROM following the PostgreSQL syntax. Increase the maximum size of database files to 281 TB. Extended the PRAGMA integrity_check statement so that it can optionally be limited to verifying just a single table and its indexes, rather than the entire database file. Added the decimal extension for doing arbitrary-precision decimal arithmetic. Enhancements to the ieee754 extension for working with IEEE 754 binary64 numbers. CLI enhancements: Added four new output modes: "box", "json", "markdown", and "table". The "column" output mode automatically expands columns to contain the longest output row and automatically turns ".header" on if it has not been previously set. The "quote" output mode honors ".separator" The decimal extension and the ieee754 extension are built-in to the CLI Query planner improvements: Add the ability to find a full-index-scan query plan for queries using INDEXED BY which previously would fail with "no query solution". Do a better job of detecting missing, incomplete, and/or dodgy sqlite_stat1 data and generates good query plans in spite of the misinformation. Improved performance of queries like "SELECT min(x) FROM t WHERE y IN (?,?,?)" assuming an index on t(x,y). In WAL mode, if a writer crashes and leaves the shm file in an inconsistent state, subsequent transactions are now able to recover the shm file even if there are active read transactions. Before this enhancement, shm file recovery that scenario would result in an SQLITE_PROTOCOL error.
sqlite3: updated to 3.32.3 3.32.3: Various minor bug fixes
sqlite3: updated to 3.32.2 3.32.2: Fix a long-standing bug in the byte-code engine that can cause a COMMIT command report as success when in fact it failed to commit.
sqlite3: updated to 3.32.1 Changes in version 3.32.1: Fix two long-standing bugs that allow malicious SQL statements to crash the process that is running SQLite. These bugs were announced by a third-party approximately 24 hours after the 3.32.0 release but are not specific to the 3.32.0 release. Other minor compiler-warning fixes and whatnot.
sqlite3: updated to 3.32.0 SQLite Release 3.32.0: Added support for approximate ANALYZE using the PRAGMA analysis_limit command. Added the bytecode virtual table. Add the checksum VFS shim to the set of run-time loadable extensions included in the source tree. Added the iif() SQL function. INSERT and UPDATE statements now always apply column affinity before computing CHECK constraints. This bug fix could, in theory, cause problems for legacy databases with unorthodox CHECK constraints the require the input type for an INSERT is different from the declared column type. See ticket 86ba67afafded936 for more information. Added the sqlite3_create_filename(), sqlite3_free_filename(), and sqlite3_database_file_object() interfaces to better support of VFS shim implementations. Increase the default upper bound on the number of parameters from 999 to 32766. Added code for the UINT collating sequence as an optional loadable extension. Enhancements to the CLI: Add options to the .import command: --csv, --ascii, --skip The .dump command now accepts multiple LIKE-pattern arguments and outputs the union of all matching tables. Add the .oom command in debugging builds Add the --bom option to the .excel, .output, and .once commands. Enhance the .filectrl command to support the --schema option. The UINT collating sequence extension is automatically loaded The ESCAPE clause of a LIKE operator now overrides wildcard characters, so that the behavior now matches what PostgreSQL does.
sqlite3: updated to 3.31.1 SQLite Release 3.31.1: Revert the data layout for an internal-use-only SQLite data structure. Applications that use SQLite should never reference internal SQLite data structures, but some do anyhow, and a change to one such data structure in 3.30.0 broke a popular and widely-deployed application. Reverting that change in SQLite, at least temporarily, gives developers of misbehaving applications time to fix their code. Fix a typos in the sqlite3ext.h header file that prevented the sqlite3_stmt_isexplain() and sqlite3_value_frombind() interfaces from being called from run-time loadable extensions.
sqlite3: updated to 3.31.0 SQLite Release 3.31.0: Add support for generated columns. Add the sqlite3_hard_heap_limit64() interface and the corresponding PRAGMA hard_heap_limit command. Enhance the function_list pragma to show the number of arguments on each function, the type of function (scalar, aggregate, window), and the function property flags SQLITE_DETERMINISTIC, SQLITE_DIRECTONLY, SQLITE_INNOCUOUS, and/or SQLITE_SUBTYPE. Add the aggregated mode feature to the DBSTAT virtual table. Add the SQLITE_OPEN_NOFOLLOW option to sqlite3_open_v2() that prevents SQLite from opening symbolic links. Added the "#-N" array notation for JSON function path arguments. Added the SQLITE_DBCONFIG_TRUSTED_SCHEMA connection setting which is also controllable via the new trusted_schema pragma and at compile-time using the -DSQLITE_TRUSTED_SCHEMA compile-time option. Added APIs sqlite3_filename_database(), sqlite3_filename_journal(), and sqlite3_filename_wal() which are useful for specialized extensions. Add the sqlite3_uri_key() interface. Upgraded the sqlite3_uri_parameter() function so that it works with the rollback journal or WAL filename in addition to the database filename. Provide the ability to tag application-defined SQL functions with new properties SQLITE_INNOCUOUS or SQLITE_DIRECTONLY. Add new verbs to sqlite3_vtab_config() so that the xConnect method of virtual tables can declare the virtual table as SQLITE_VTAB_INNOCUOUS or SQLITE_VTAB_DIRECTONLY. Faster response to sqlite3_interrupt(). Added the uuid.c extension module implementing functions for processing RFC-4122 UUIDs. The lookaside memory allocator is enhanced to support two separate memory pools with different sized allocations in each pool. This allows more memory allocations to be covered by lookaside while at the same time reducing the heap memory usage to 48KB per connection, down from 120KB. The legacy_file_format pragma is deactivated. It is now a no-op. In its place, the SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option to sqlite3_db_config() is provided. The legacy_file_format pragma is deactivated because (1) it is rarely useful and (2) it is incompatible with VACUUM in schemas that have tables with both generated columns and descending indexes.
sqlite3: updated to 3.30.1 SQLite Release 3.30.1: Fix a bug in the query flattener that might cause a segfault for nested queries that use the new FILTER clause on aggregate functions. Cherrypick fixes for other obscure problems found since the 3.30.0 release.
sqlite3: updated to 3.30.0 SQLite Release 3.30.0 Add support for the FILTER clause on aggregate functions. Add support for the NULLS FIRST and NULLS LAST syntax in ORDER BY clauses. The index_info and index_xinfo pragmas are enhanced to provide information about the on-disk representation of WITHOUT ROWID tables. Add the sqlite3_drop_modules() interface, allowing applications to disable automatically loaded virtual tables that they do not need. Improvements to the .recover dot-command in the CLI so that it recovers more content from corrupt database files. Enhance the RBU extension to support indexes on expressions. Change the schema parser so that it will error out if any of the type, name, and tbl_name columns of the sqlite_master table have been corrupted and the database connection is not in writable_schema mode. The PRAGMA function_list, PRAGMA module_list, and PRAGMA pragma_list commands are now enabled in all builds by default. Disable them using -DSQLITE_OMIT_INTROSPECTION_PRAGMAS. Add the SQLITE_DBCONFIG_ENABLE_VIEW option for sqlite3_db_config(). Added the TCL Interface config method in order to be able to disable SQLITE_DBCONFIG_ENABLE_VIEW as well as control other sqlite3_db_config() options from TCL. Added the SQLITE_DIRECTONLY flag for application-defined SQL functions to prevent those functions from being used inside triggers and views. The legacy SQLITE_ENABLE_STAT3 compile-time option is now a no-op.
sqlite3: updated to 3.29.0 SQLite Release 3.29.0: Added the SQLITE_DBCONFIG_DQS_DML and SQLITE_DBCONFIG_DQS_DDL actions to sqlite3_db_config() for activating and deactivating the double-quoted string literal misfeature. Both default to "on" for legacy compatibility, but developers are encouraged to turn them "off", perhaps using the -DSQLITE_DQS=0 compile-time option. -DSQLITE_DQS=0 is now a recommended compile-time option. Improvements to the query planner: Improved optimization of AND and OR operators when one or the other operand is a constant. Enhancements to the LIKE optimization for cases when the left-hand side column has numeric affinity. Added the "sqlite_dbdata" virtual table for extracting raw low-level content from an SQLite database, even a database that is corrupt. Enhancements to the CLI: Add the ".recover" command which tries to recover as much content as possible from a corrupt database file. Add the ".filectrl" command useful for testing. Add the long-standing ".testctrl" command to the ".help" menu. Added the ".dbconfig" command
sqlite3: updated to 3.28.0 SQLite Release 3.28.0: Enhanced window functions: Add support the EXCLUDE clause. Add support for window chaining. Add support for GROUPS frames. Add support for "<expr> PRECEDING" and "<expr> FOLLOWING" boundaries in RANGE frames. Added the new sqlite3_stmt_isexplain(S) interface for determining whether or not a prepared statement is an EXPLAIN. Enhanced VACUUM INTO so that it works for read-only databases. New query optimizations: Enable the LIKE optimization for cases when the ESCAPE keyword is present and PRAGMA case_sensitive_like is on. In queries that are driven by a partial index, avoid unnecessary tests of the constraint named in the WHERE clause of the partial index, since we know that constraint must always be true. Enhancements to the TCL Interface: Added the -returntype option to the function method. Added the new bind_fallback method. Enhancements to the CLI: Added support for bound parameters and the .parameter command. Fix the readfile() function so that it returns an empty BLOB rather than throwing an out-of-memory error when reading an empty file. Fix the writefile() function so that when it creates new directories along the path of a new file, it gives them umask permissions rather than the same permissions as the file. Change --update option in the .archive command so that it skips files that are already in the archive and are unchanged. Add the new --insert option that works like --update used to work. Added the fossildelta.c extension that can create, apply, and deconstruct the Fossil DVCS file delta format that is used by the RBU extension. Added the SQLITE_DBCONFIG_WRITABLE_SCHEMA verb for the sqlite3_db_config() interface, that does the same work as PRAGMA writable_schema without using the SQL parser. Added the sqlite3_value_frombind() API for determining if the argument to an SQL function is from a bound parameter. Security and compatibilities enhancements to fts3_tokenizer(): The fts3_tokenizer() function always returns NULL unless either the legacy application-defined FTS3 tokenizers interface are enabled using the sqlite3_db_config(SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER) setting, or unless the first argument to fts3_tokenizer() is a bound parameter. The two-argument version of fts3_tokenizer() accepts a pointer to the tokenizer method object even without the sqlite3_db_config(SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER) setting if the second argument is a bound parameter Improved robustness against corrupt database files. Miscellaneous performance enhancements
sqlite3: updated to 3.27.2 SQLite Release 3.27.2: Fix a bug in the IN operator that was introduced by an attempted optimization in version 3.27.0. Fix a bug causing a crash when a window function is misused. Fix various documentation typos
sqlite3: updated to 3.27.1 SQLite Release 3.27.1: Fix a bug in the query optimizer: an adverse interaction between the OR optimization and the optimization that tries to use values read directly from an expression index instead of recomputing the expression. Hashes: Changes carried forward from version 3.27.0: Added the VACUUM INTO command Issue an SQLITE_WARNING message on the error log if a double-quoted string literal is used. The sqlite3_normalized_sql() interface works on any prepared statement created using sqlite3_prepare_v2() or sqlite3_prepare_v3(). It is no longer necessary to use sqlite3_prepare_v3() with SQLITE_PREPARE_NORMALIZE in order to use sqlite3_normalized_sql(). Added the remove_diacritics=2 option to FTS3 and FTS5. Added the SQLITE_PREPARE_NO_VTAB option to sqlite3_prepare_v3(). Use that option to prevent circular references to shadow tables from causing resource leaks. Enhancements to the sqlite3_deserialize() interface: Add the SQLITE_FCNTL_SIZE_LIMIT file-control for setting an upper bound on the size of the in-memory database created by sqlite3_deserialize. The default upper bound is 1GiB, or whatever alternative value is specified by sqlite3_config(SQLITE_CONFIG_MEMDB_MAXSIZE) and/or SQLITE_MEMDB_DEFAULT_MAXSIZE. Honor the SQLITE_DESERIALIZE_READONLY flag, which was previously described in the documentation, but was previously a no-op. Enhance the "deserialize" command of the TCL Interface to give it new "--maxsize N" and "--readonly BOOLEAN" options. Enhancements to the CLI, mostly to support testing and debugging of the SQLite library itself: Add support for ".open --hexdb". The "dbtotxt" utility program used to generate the text for the "hexdb" is added to the source tree. Add support for the "--maxsize N" option on ".open --deserialize". Add the "--memtrace" command-line option, to show all memory allocations and deallocations. Add the ".eqp trace" option on builds with SQLITE_DEBUG, to enable bytecode program listing with indentation and PRAGMA vdbe_trace all in one step. Add the ".progress" command for accessing the sqlite3_progress_handler() interface. Add the "--async" option to the ".backup" command. Add options "--expanded", "--normalized", "--plain", "--profile", "--row", "--stmt", and "--close" to the ".trace" command. Increased robustness against malicious SQL that is run against a maliciously corrupted database. Bug fixes: Do not use a partial index to do a table scan on an IN operator. Fix the query flattener so that it works on queries that contain subqueries that use window functions. Ensure that ALTER TABLE modifies table and column names embedded in WITH clauses that are part of views and triggers. Fix a parser bug that prevented the use of parentheses around table-valued functions. Fix a problem with the OR optimization on indexes on expressions. Fix a problem with the LEFT JOIN strength reduction optimization in which the optimization was being applied inappropriately due to an IS NOT NULL operator. Fix the REPLACE command so that it is no longer able to sneak a NULL value into a NOT NULL column even if the NOT NULL column has a default value of NULL. Fix a problem with the use of window functions used within correlated subqueries. Fix the ALTER TABLE RENAME COLUMN command so that it works for tables that have redundant UNIQUE constraints. Fix a bug that caused zeroblob values to be truncated when inserted into a table that uses an expression index.
sqlite3: updated to 3.26.0 SQLite Release 3.26.0: Optimization: When doing an UPDATE on a table with indexes on expressions, do not update the expression indexes if they do not refer to any of the columns of the table being updated. Allow the xBestIndex() method of virtual table implementations to return SQLITE_CONSTRAINT to indicate that the proposed query plan is unusable and should not be given further consideration. Added the SQLITE_DBCONFIG_DEFENSIVE option which disables the ability to create corrupt database files using ordinary SQL. Added support for read-only shadow tables when the SQLITE_DBCONFIG_DEFENSIVE option is enabled. Added the PRAGMA legacy_alter_table command, which if enabled causes the ALTER TABLE command to behave like older version of SQLite (prior to version 3.25.0) for compatibility. Added PRAGMA table_xinfo that works just like PRAGMA table_info except that it also shows hidden columns in virtual tables. Added the explain virtual table as a run-time loadable extension. Add a limit counter to the query planner to prevent excessive sqlite3_prepare() times for certain pathological SQL inputs. Added support for the sqlite3_normalized_sql() interface, when compiling with SQLITE_ENABLE_NORMALIZE. Enhanced triggers so that they can use table-valued functions that exist in schemas other than the schema where the trigger is defined. Enhancements to the CLI: - Improvements to the ".help" command. - The SQLITE_HISTORY environment variable, if it exists, specifies the name of the command-line editing history file - The --deserialize option associated with opening a new database cause the database file to be read into memory and accessed using the sqlite3_deserialize() API. This simplifies running tests on a database without modifying the file on disk. Enhancements to the geopoly extension: - Aways stores polygons using the binary format, which is faster and uses less space. - Added the geopoly_regular() function. - Added the geopoly_ccw() function. Enhancements to the session extension: - Added the SQLITE_CHANGESETAPPLY_INVERT flag - Added the sqlite3changeset_start_v2() interface and the SQLITE_CHANGESETSTART_INVERT flag. - Added the changesetfuzz.c test-case generator utility.
sqlite3: updated to 3.25.3 SQLite Release 3.25.3: Disallow the use of window functions in the recursive part of a CTE. Fix the behavior of typeof() and length() on virtual tables. Strengthen defenses against deliberately corrupted database files. Fix a problem in the query planner that results when a row-value expression is used with a PRIMARY KEY with redundant columns. Fix the query planner so that it works correctly for IS NOT NULL operators in the ON clause of a LEFT JOIN with the SQLITE_ENABLE_STAT4 compile-time option.
sqlite3: updated to 3.25.2 SQLite Release 3.25.2: 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. 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. Fixes for various other compiler warnings and minor problems associated with obscure configurations.
sqlite3: updated to 3.25.1 SQLite Release 3.25.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. 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.
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.
sqlite3: updated to 3.24.0 SQLite Release 3.24.0: Add support for PostgreSQL-style UPSERT. Add support for auxiliary columns in r-tree tables. Add C-language APIs for discovering SQL keywords used by SQLite: sqlite3_keyword_count(), sqlite3_keyword_name(), and sqlite3_keyword_check(). Add C-language APIs for dynamic strings based on the sqlite3_str object. Enhance ALTER TABLE so that it recognizes "true" and "false" as valid arguments to DEFAULT. Add the sorter-reference optimization as a compile-time option. Only available if compiled with SQLITE_ENABLE_SORTER_REFERENCES. Improve the format of the EXPLAIN QUERY PLAN raw output, so that it gives better information about the query plan and about the relationships between the various components of the plan. Added the SQLITE_DBCONFIG_RESET_DATABASE option to the sqlite3_db_config() API. CLI Enhancements: Automatically intercepts the raw EXPLAIN QUERY PLAN output and reformats it into an ASCII-art graph. Lines that begin with "#" and that are not in the middle of an SQL statement are interpreted as comments. Added the --append option to the ".backup" command. Added the ".dbconfig" command. Performance: UPDATE avoids unnecessary low-level disk writes when the contents of the database file do not actually change. For example, "UPDATE t1 SET x=25 WHERE y=?" generates no extra disk I/O if the value in column x is already 25. Similarly, when doing UPDATE on records that span multiple pages, only the subset of pages that actually change are written to disk. This is a low-level performance optimization only and does not affect the behavior of TRIGGERs or other higher level SQL structures. Queries that use ORDER BY and LIMIT now try to avoid computing rows that cannot possibly come in under the LIMIT. This can greatly improve performance of ORDER BY LIMIT queries, especially when the LIMIT is small relative to the number of unrestricted output rows. The OR optimization is allowed to proceed even if the OR expression has also been converted into an IN expression. Uses of the OR optimization are now also more clearly shown in the EXPLAIN QUERY PLAN output. The query planner is more aggressive about using automatic indexes for views and subqueries for which it is not possible to create a persistent index. Make use of the one-pass UPDATE and DELETE query plans in the R-Tree extension where appropriate. Performance improvements in the LEMON-generated parser. Bug fixes: For the right-hand table of a LEFT JOIN, compute the values of expressions directly rather than loading precomputed values out of an expression index as the expression index might not contain the correct value. Do not attempt to use terms from the WHERE clause to enable indexed lookup of the right-hand table of a LEFT JOIN. Fix a memory leak that can occur following a failure to open error in the CSV virtual table Fix a long-standing problem wherein a corrupt schema on the sqlite_sequence table used by AUTOINCREMENT can lead to a crash. Fix the json_each() function so that it returns valid results on its "fullkey" column when the input is a simple value rather than an array or object.
sqlite: updated to 3.23.1 SQLite Release 3.23.1: Fix two problems in the new LEFT JOIN strength reduction optimization. Fix misbehavior of the FTS5 xBestIndex method. Fix a harmless reference to an uninitialized virtual machine register. Fix the CLI so that it builds with -DSQLITE_UNTESTABLE Fix the eval.c extension so that it works with PRAGMA empty_result_callbacks=ON. Fix the generate_series virtual table so that it correctly returns no rows if any of its constraints are NULL. Performance enhancements in the parser.
sqlite3: updated to 3.23.0
SQLite Release 3.23.0:
Add the sqlite3_serialize() and sqlite3_deserialize() interfaces when the SQLITE_ENABLE_DESERIALIZE compile-time option is used.
Recognize TRUE and FALSE as constants. (For compatibility, if there exist columns named "true" or "false", then the identifiers refer to the columns rather than Boolean constants.)
Support operators IS TRUE, IS FALSE, IS NOT TRUE, and IS NOT FALSE.
Added the SQLITE_DBSTATUS_CACHE_SPILL option to sqlite3_db_status() for reporting the number of cache spills that have occurred.
The "alternate-form-2" flag ("!") on the built-in printf implementation now causes string substitutions to measure the width and precision in characters instead of bytes.
If the xColumn method in a virtual table implementation returns an error message using sqlite3_result_error() then give that error message preference over internally-generated messages.
Added the -A command-line option to the CLI to make it easier to manage SQLite Archive files.
Add support for INSERT OR REPLACE, INSERT OR IGNORE, and UPDATE OR REPLACE in the Zipfile virtual table.
Enhance the sqlite3changeset_apply() interface so that it is hardened against attacks from deliberately corrupted changeset objects.
Added the sqlite3_normalize() extension function.
Query optimizer enhancements:
Improve the omit-left-join optimization so that it works in cases where the right-hand table is UNIQUE but not necessarily NOT NULL.
Improve the push-down optimization so that it works for many LEFT JOINs.
Add the LEFT JOIN strength reduction optimization that converts a LEFT JOIN into an ordinary JOIN if there exist terms in the WHERE clause that would prevent the extra all-NULL row of the LEFT JOIN from appearing in the output set.
Avoid unnecessary writes to the sqlite_sequence table when an AUTOINCREMENT table is updated with an rowid that is less than the maximum.
Bug fixes:
Fix the parser to accept valid row value syntax.
Fix the query planner so that it takes into account dependencies in the arguments to table-valued functions in subexpressions in the WHERE clause.
Fix incorrect result with complex OR-connected WHERE and STAT4.
Fix potential corruption in indexes on expressions due to automatic datatype conversions.
Assertion fault in FTS4.
Incorrect result on the less-than operator in row values.
Always interpret non-zero floating-point values as TRUE, even if the integer part is zero.
Fix an issue in the fsdir(PATH) table-valued function to the fileio.c extension, that caused a segfault if the fsdir() table was used as the inner table of a join.
Issue an error rather instead of an assertion-fault or null-pointer dereference when the sqlite_master table is corrupted so that the sqlite_sequence table root page is really a btree-index page.
Fix the ANALYZE command so that it computes statistics on tables whose names begin with "sqlite".
Additional fixes for issues detected by OSSFuzz:
Fix a possible infinite loop on VACUUM for corrupt database files.
Disallow parameters in the WITH clause of triggers and views.
Fix a potential memory leak in row value processing.
Improve the performance of the replace() SQL function for cases where there are many substitutions on megabyte-sized strings, in an attempt to avoid OSSFuzz timeouts during testing.
Provide an appropriate error message when the sqlite_master table contains a CREATE TABLE AS statement. Formerly this caused either an assertion fault or null pointer dereference. Problem found by OSSFuzz on the GDAL project.
Incorrect assert() statement removed.
Fix a problem with using the LIKE optimization on an INTEGER PRIMARY KEY.
sqlite3: updated to 3.22.0 Release 3.22.0: The output of sqlite3_trace_v2() now shows each individual SQL statement run within a trigger. Add the ability to read from WAL mode databases even if the application lacks write permission on the database and its containing directory, as long as the -shm and -wal files exist in that directory. Added the rtreecheck() scalar SQL function to the R-Tree extension. Added the sqlite3_vtab_nochange() and sqlite3_value_nochange() interfaces to help virtual table implementations optimize UPDATE operations. Added the sqlite3_vtab_collation() interface. Added support for the "^" initial token syntax in FTS5. New extensions: The Zipfile virtual table can read and write a ZIP Archive. Added the fsdir(PATH) table-valued function to the fileio.c extension, for listing the files in a directory. The sqlite_btreeinfo eponymous virtual table for introspecting and estimating the sizes of the btrees in a database. The Append VFS is a VFS shim that allows an SQLite database to be appended to some other file. This allows (for example) a database to be appended to an executable that then opens and reads the database. Query planner enhancements: The optimization that uses an index to quickly compute an aggregate min() or max() is extended to work with indexes on expressions. The decision of whether to implement a FROM-clause subquery as a co-routine or using query flattening now considers whether the result set of the outer query is "complex" (if it contains functions or expression subqueries). A complex result set biases the decision toward the use of co-routines. The planner avoids query plans that use indexes with unknown collating functions. The planner omits unused LEFT JOINs even if they are not the right-most joins of a query. Other performance optimizations: A smaller and faster implementation of text to floating-point conversion subroutine: sqlite3AtoF(). The Lemon parser generator creates a faster parser. Use the strcspn() C-library routine to speed up the LIKE and GLOB operators. Improvements to the command-line shell: The ".schema" command shows the structure of virtual tables. Added support for reading and writing SQL Archive files using the .archive command. Added the experimental .expert command Added the ".eqp trigger" variant of the ".eqp" command Enhance the ".lint fkey-indexes" command so that it works with WITHOUT ROWID tables. If the filename argument to the shell is a ZIP archive rather than an SQLite database, then the shell automatically opens that ZIP archive using the Zipfile virtual table. Added the edit() SQL function. Added the .excel command to simplify exporting database content to a spreadsheet. Databases are opened using Append VFS when the --append flag is used on the command line or with the .open command. Enhance the SQLITE_ENABLE_UPDATE_DELETE_LIMIT compile-time option so that it works for WITHOUT ROWID tables. Provide the sqlite_offset(X) SQL function that returns the byte offset into the database file to the beginning of the record holding value X, when compiling with -DSQLITE_ENABLE_OFFSET_SQL_FUNC. Bug fixes
sqlite3: updated to 3.21.0 Release 3.21.0: Take advantage of the atomic-write capabilities in the F2FS filesystem when available, for greatly reduced transaction overhead. This currently requires the SQLITE_ENABLE_BATCH_ATOMIC_WRITE compile-time option. Allow ATTACH and DETACH commands to work inside of a transaction. Allow WITHOUT ROWID virtual tables to be writable if the PRIMARY KEY contains exactly one column. The "fsync()" that occurs after the header is written in a WAL reset now uses the sync settings for checkpoints. This means it will use a "fullfsync" on macs if PRAGMA checkpoint_fullfsync set on. The sqlite3_sourceid() function tries to detect if the source code has been modified from what is checked into version control and if there are modifications, the last four characters of the version hash are shown as "alt1" or "alt2". The objective is to detect accidental and/or careless edits. A forger can subvert this feature. Improved de-quoting of column names for CREATE TABLE AS statements with an aggregate query on the right-hand side. Fewer "stat()" system calls issued by the unix VFS. Enhanced the LIKE optimization so that it works with an ESCAPE clause. Enhanced PRAGMA integrity_check and PRAGMA quick_check to detect obscure row corruption that they were formerly missing. Also update both pragmas so that they return error text rather than SQLITE_CORRUPT when encountering corruption in records. The query planner now prefers to implement FROM-clause subqueries using co-routines rather using the query flattener optimization. Support for the use of co-routines for subqueries may no longer be disabled. Pass information about !=, IS, IS NOT, NOT NULL, and IS NULL constraints into the xBestIndex method of virtual tables. Enhanced the CSV virtual table so that it accepts the last row of input if the final new-line character is missing. Remove the rarely-used "scratch" memory allocator. Replace it with the SQLITE_CONFIG_SMALL_MALLOC configuration setting that gives SQLite a hint that large memory allocations should be avoided when possible. Added the swarm virtual table to the existing union virtual table extension. Added the sqlite_dbpage virtual table for providing direct access to pages of the database file. The source code is built into the amalgamation and is activated using the -DSQLITE_ENABLE_DBPAGE_VTAB compile-time option. Add a new type of fts5vocab virtual table - "instance" - that provides direct access to an FTS5 full-text index at the lowest possible level. Remove a call to rand_s() in the Windows VFS since it was causing problems in Firefox on some older laptops. The src/shell.c source code to the command-line shell is no longer under version control. That file is now generated as part of the build process. Miscellaneous microoptimizations reduce CPU usage by about 2.1%. Bug fixes
Release 3.20.1: Fix a potential memory leak in the new sqlite3_result_pointer() interface.
Release 3.20.0: 1. Update the text of error messages returned by sqlite3_errmsg() for some error codes. 2. Add new pointer passing interfaces. 3. Backwards-incompatible changes to some extensions in order to take advantage of the improved security offered by the new pointer passing interfaces: a. Extending FTS5 → requires sqlite3_bind_pointer() to find the fts5_api pointer. b. carray(PTR,N) → requires sqlite3_bind_pointer() to set the PTR parameter. c. remember(V,PTR) → requires sqlite3_bind_pointer() to set the PTR parameter. 4. Added the SQLITE_STMT virtual table extension. 5. Added the COMPLETION extension - designed to suggest tab-completions for interactive user interfaces. This is a work in progress. Expect further enhancements in future releases. 6. Added the UNION virtual table extension. 7. The built-in date and time functions have been enhanced so that they can be used in CHECK constraints, in indexes on expressions, and in the WHERE clauses of partial indexes, provided that they do not use the 'now', 'localtime', or 'utc' keywords. Futher information. 8. Added the sqlite3_prepare_v3() and sqlite3_prepare16_v3() interfaces with the extra "prepFlags" parameters. 9. Provide the SQLITE_PREPARE_PERSISTENT flag for sqlite3_prepare_v3() and use it to limit lookaside memory misuse by FTS3, FTS5, and the R-Tree extension. 10. Added the PRAGMA secure_delete=FAST command. When secure_delete is set to FAST, old content is overwritten with zeros as long as that does not increase the amount of I/O. Deleted content might still persist on the free-page list but will be purged from all b-tree pages. 11. Enhancements to the command-line shell: a. Add support for tab-completion using the COMPLETION extension, for both readline and linenoise. b. Add the ".cd" command. c. Enhance the ".schema" command to show the schema of all attached databases. d. Enhance ".tables" so that it shows the schema names for all attached if the name is anything other than "main". e. The ".import" command ignores an initial UTF-8 BOM. f. Added the "--newlines" option to the ".dump" command to cause U+000a and U+000d characters to be output literally rather than escaped using the replace() function. 12. Query planner enhancements: a. When generating individual loops for each ORed term of an OR scan, move any constant WHERE expressions outside of the loop, as is done for top-level loops. b. The query planner examines the values of bound parameters to help determine if a partial index is usable. c. When deciding between two plans with the same estimated cost, bias the selection toward the one that does not use the sorter. d. Evaluate WHERE clause constraints involving correlated subqueries last, in the hope that they never have be evaluated at all. e. Do not use the flattening optimization for a sub-query on the RHS of a LEFT JOIN if that subquery reads data from a virtual table as doing so prevents the query planner from creating automatic indexes on the results of the sub-query, which can slow down the query. 13. Add SQLITE_STMTSTATUS_REPREPARE, SQLITE_STMTSTATUS_RUN, and SQLITE_STMTSTATUS_MEMUSED options for the sqlite3_stmt_status() interface. 14. Provide PRAGMA functions for PRAGMA integrity_check, PRAGMA quick_check, and PRAGMA foreign_key_check. 15. Add the -withoutnulls option to the TCL interface eval method. 16. Enhance the sqlite3_analyzer.exe utility program so that it shows the number of bytes of metadata on btree pages. 17. The SQLITE_DBCONFIG_ENABLE_QPSG run-time option and the SQLITE_ENABLE_QPSG compile-time option enable the query planner stability guarantee. See also ticket 892fc34f173e99d8 18. Miscellaneous optimizations result in a 2% reduction in CPU cycles used. Bug Fixes: 19. Fix the behavior of sqlite3_column_name() for queries that use the flattening optimization so that the result is consistent with other queries that do not use that optimization, and with PostgreSQL, MySQL, and SQLServer. Ticket de3403bf5ae. 20. Fix the query planner so that it knows not to use automatic indexes on the right table of LEFT JOIN if the WHERE clause uses the IS operator. Fix for ce68383bf6aba. 21. Ensure that the query planner knows that any column of a flattened LEFT JOIN can be NULL even if that column is labeled with "NOT NULL". Fix for ticket 892fc34f173e99d8. 22. Fix rare false-positives in PRAGMA integrity_check when run on a database connection with attached databases. Ticket a4e06e75a9ab61a12 23. Fix a bug (discovered by OSSFuzz) that causes an assertion fault if certain dodgy CREATE TABLE declarations are used.
Release 3.19.3: Fix a bug associated with auto_vacuum that can lead to database corruption. The bug was introduced in version 3.16.0.
SQLite Release 3.19.2 On 2017-05-25 Fix more bugs in the LEFT JOIN flattening optimization. Ticket 7fde638e94287d2c. Changes carried forward from version 3.19.1 (2017-05-24): Fix a bug in the LEFT JOIN flattening optimization. Ticket cad1ab4cb7b0fc. Remove a surplus semicolon that was causing problems for older versions of MSVC.
Match sqlite3 version
Follow sqlite3 version
SQLite Release 3.17.0 On 2017-02-13 * Approximately 25% better performance from the R-Tree extension. * Uses compiler built-ins (ex: __builtin_bswap32() or _byteswap_ulong()) for byteswapping when available. * Uses the sqlite3_blob key/value access object instead of SQL for pulling content out of R-Tree nodes * Other miscellaneous enhancements such as loop unrolling. * Add the SQLITE_DEFAULT_LOOKASIDE compile-time option. * Increase the default lookaside size from 512,125 to 1200,100 as this provides better performance while only adding 56KB of extra memory per connection. Memory-sensitive applications can restore the old default at compile-time, start-time, or run-time. * Use compiler built-ins __builtin_sub_overflow(), __builtin_add_overflow(), and __builtin_mul_overflow() when available. (All compiler built-ins can be omitted with the SQLITE_DISABLE_INTRINSIC compile-time option.) * Added the SQLITE_ENABLE_NULL_TRIM compile-time option, which can result in significantly smaller database files for some applications, at the risk of being incompatible with older versions of SQLite. * Change SQLITE_DEFAULT_PCACHE_INITSZ from 100 to 20, for improved performance. * Added the SQLITE_UINT64_TYPE compile-time option as an analog to SQLITE_INT64_TYPE. * Perform some UPDATE operations in a single pass instead of in two passes. * Enhance the session extension to support WITHOUT ROWID tables. * Fixed performance problems and potential stack overflows when creating views from multi-row VALUES clauses with hundreds of thousands of rows. * Added the sha1.c extension. * In the command-line shell, enhance the ".mode" command so that it restores the default column and row separators for modes "line", "list", "column", and "tcl". * Enhance the SQLITE_DIRECT_OVERFLOW_READ option so that it works in WAL mode as long as the pages being read are not in the WAL file. * Enhance the LEMON parser generator so that it can store the parser object as a stack variable rather than allocating space from the heap and make use of that enhancement in the amalgamation. * Other performance improvements. Uses about 6.5% fewer CPU cycles. Bug Fixes: * Throw an error if the ON clause of a LEFT JOIN references tables to the right of the ON clause. This is the same behavior as PostgreSQL. Formerly, SQLite silently converted the LEFT JOIN into an INNER JOIN. * Use the correct affinity for columns of automatic indexes. * Ensure that the sqlite3_blob_reopen() interface can correctly handle short rows.
Changes 3.16.2: Fix the REPLACE statement for WITHOUT ROWID tables that lack secondary indexes so that it works correctly with triggers and foreign keys. This was a new bug caused by performance optimizations added in version 3.16.0. Ticket 30027b613b4 Fix the sqlite3_value_text() interface so that it correctly translates content generated by zeroblob() into a string of all 0x00 characters. This is a long-standing issue discovered after the 3.16.1 release by OSS-Fuzz Fix the bytecode generator to deal with a subquery in the FROM clause that is itself a UNION ALL where one side of the UNION ALL is a view that contains an ORDER BY. This is a long-standing issue that was discovered after the release of 3.16.1. See ticket 190c2507. Adjust the sqlite3_column_count() API so it more often returns the same values for PRAGMA statements as it did in prior releases, to minimize disruption to applications that might be using that interface in unexpected ways.
SQLite Release 3.16.0 On 2017-01-02 Uses 9% fewer CPU cycles. (See the CPU performance measurement report for details on how the this performance increase was computed.) Added experimental support for PRAGMA functions. Added the SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE option to sqlite3_db_config(). Enhance the date and time functions so that the 'unixepoch' modifier works for the full span of supported dates. Changed the default configuration of the lookaside memory allocator from 500 slots of 128 bytes each into 125 slots of 512 bytes each. Enhanced "WHERE x NOT NULL" partial indexes so that they are usable if the "x" column appears in a LIKE or GLOB operator. Enhanced sqlite3_interrupt() so that it interrupts checkpoint operations that are in process. Enhanced the LIKE and GLOB matching algorithm to be faster for cases when the pattern contains multiple wildcards. Added the SQLITE_FCNTL_WIN32_GET_HANDLE file control opcode. Added ".mode quote" to the command-line shell. Added ".lint fkey-indexes" to the command-line shell. Added the .imposter dot-command to the command-line shell. Added the remember(V,PTR) SQL function as a loadable extension. Rename the SQLITE_OMIT_BUILTIN_TEST compile-time option to SQLITE_UNTESTABLE to better reflect the implications of using it. Bug Fixes: Fix a long-standing bug in the query planner that caused incorrect results on a LEFT JOIN where the left-hand table is a subquery and the join constraint is a bare column name coming from the left-hand subquery. Ticket 2df0107b. Correctly handle the integer literal -0x8000000000000000 in the query planner.
SQLite Release 3.15.2 * Multiple bug fixes to the row value logic that was introduced in version 3.15.0. * Fix a NULL pointer dereference in ATTACH/DETACH following a maliciously constructed syntax error. * Fix a crash that can occur following an out-of-memory condition in the built-in instr() function. * In the JSON extension, fix the JSON validator so that it correctly rejects invalid backslash escapes within strings.
Sync with sqlite3.15.1
Upgrade lemon 1.0 from sqlite 3.5.9 to lemon 1.0 from sqlite 3.15.0 pkgsrc changes ============== Bind this package with databases/sqlite3 to get immediate updates along with the sqlite3 package. Set new versioning policy and concatenate versions of lemon and sqlite3. The reasoning for it is as follows: - currently lemon is an integral part of sqlite3 - lemon has its own conservative versioning regardless of changes in its code - leave room for possible standalone lemon package with bumped versions - reflect reality and make it human readable without checking the sources Set LICENSE to public-domain. Install documentation in the HTML format. Compile with LDFLAGS set. Finally don't use databases/sqlite3/Makefile.common as lemon is not distributed in the same archive. Make use of Makefile.version that does the same job of tracking upstream. Do not set PKGCONFIG_OVERRIDE in Makefile.common, it is not accessible in sqlite3-tcl. Upstream changelog ================== Changes are unknown, but at least the program acquired a -T command line option used by brlcad.
Add SHA512 digests for distfiles for devel category Issues found with existing distfiles: distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip distfiles/fortran-utils-1.1.tar.gz distfiles/ivykis-0.39.tar.gz distfiles/enum-1.11.tar.gz distfiles/pvs-3.2-libraries.tgz distfiles/pvs-3.2-linux.tgz distfiles/pvs-3.2-solaris.tgz distfiles/pvs-3.2-system.tgz No changes made to these distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
Import cleaned up lemon-1.0 from pkgsrc-wip: Lemon is a simple LALR(1) parser generator, creating both re-entrant and thread-safe parsers.
Initial revision