Changelog for sqlite3-tcl-3.41.0-3.2.x86_64.rpm :

* Wed Feb 22 2023 Reinhard Max - Update to 3.41.0:
* https://www.sqlite.org/releaselog/3_41_0.html
* Various query planner improvements.
* 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.
* In-memory databases created using sqlite3_deserialize() now report their filename as an empty string, not as \'x\'.
* The \".scanstats est\" command provides query planner estimates in profiles.
* Enhance the --safe command-line option to disallow dangerous SQL functions.
* The double-quoted string misfeature is now disabled by default for CLI builds.
* Various other improvements and performance enhancements.- The new version obsoletes sqlite-src-3390000-func7-pg-181.patch
* Wed Dec 28 2022 Andreas Stieger - Update to 3.40.1:
* 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. (previously patched, drop sqlite-CVE-2022-46908.patch)
* 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.
* Tue Dec 13 2022 Reinhard Max - bsc#1206337, CVE-2022-46908, sqlite-CVE-2022-46908.patch: relying on --safe for execution of an untrusted CLI script
* Thu Nov 17 2022 Reinhard Max - update to 3.40.0:
* https://sqlite.org/releaselog/3_40_0.html
* Add support for compiling SQLite to WASM and running it in wen browsers.
* Add the recovery extension that might be able to recover some content from a corrupt database file.
* For more changes, see https://sqlite.org/releaselog/3_40_0.html
* Wed Nov 02 2022 Andreas Stieger - update to 3.39.4:
* 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
* Mon Sep 05 2022 Reinhard Max - update to 3.39.3:
* 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.
* Use a mutex to protect the PRAGMA temp_store_directory and PRAGMA data_store_directory statements, even though they are decremented and documented as not being threadsafe.
* Thu Jul 21 2022 Reinhard Max - update to 3.39.2:
* 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. [boo#1201783]
* Fri Jul 15 2022 Andreas Stieger - update to 3.39.1:
* 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
* 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 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.
* Fri Jul 01 2022 Andreas Stieger - update to 3.39.0:
* 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%.- drop sqlite-src-3380100-atof1.patch, included upstream- add sqlite-src-3390000-func7-pg-181.patch to skip float precision related test failures on 32 bit
* Sun May 08 2022 Andreas Stieger - update to 3.38.5:
* Fix a blunder in the CLI of the 3.38.4 release- includes changes from 3.38.4:
* 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
* Thu Apr 28 2022 Paolo Stivanin - update to 3.38.3:
* 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.
* Other minor patches. See the timeline for details.
* Tue Mar 29 2022 Reinhard Max - update to 3.38.2:
* Fix a problem with the 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.
* Other minor patches.
* Wed Mar 16 2022 Reinhard Max - Remove obsolete configure flags- Package the Tcl bindings here again so that we only ship one copy of SQLite (bsc#1195773).
* Sun Mar 13 2022 Andreas Stieger - update to 3.38.1:
* 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. See the source code timeline for details.- add upstream patch to run atof1 tests only on x86_64 sqlite-src-3380100-atof1.patch
* Sat Feb 26 2022 Andreas Stieger - update to 3.38.0
* Add the -> and ->> operators for easier processing of JSON
* The JSON functions are now built-ins
* Enhancements to date and time functions
* Rename the printf() SQL function to format() for better compatibility, with alias for backwards compatibility.
* Add the sqlite3_error_offset() interface for helping localize an SQL error to a specific character in the input SQL text
* Enhance the interface to virtual tables
* CLI columnar output modes are enhanced to correctly handle tabs and newlines embedded in text, and add options like \"--wrap N\", \"--wordwrap on\", and \"--quote\" to the columnar output modes.
* Query planner enhancements using a Bloom filter to speed up large analytic queries, and 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
* Wed Jan 12 2022 Andreas Stieger - update to 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
* 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
* Sun Jan 02 2022 Andreas Stieger - update to 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.
* Tue Nov 30 2021 Reinhard Max - SQLite3 3.37.0:
* 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.
* 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.
* CLI: 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.
* bsc#1189802, CVE-2021-36690: Fix an issue with the SQLite Expert extension when a column has no collating sequence.
* Tue Jun 22 2021 Paolo Stivanin - SQLite3 3.36.0:
* 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 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.
* Tue Apr 20 2021 Andreas Stieger - SQLite3 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
* Tue Apr 06 2021 Reinhard Max - Fix build on SLE-12
* Tue Apr 06 2021 Dirk Müller - use https urls
* Sat Apr 03 2021 Andreas Stieger - SQLite 3.35.4:
* Fix a defect in the query planner optimization
* 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
* Sat Mar 27 2021 Andreas Stieger - SQLite 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
* 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)
* Improvements to error messages generated by faulty common table expressions
* Fix some incorrect assert() statements
* Fix to the SELECT statement syntax diagram so that the FROM clause syntax is shown correctly
* Fix the EBCDIC character classifier so that it understands newlines as whitespace
* 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
* Fri Mar 19 2021 Martin Liška - Fix typo in macro definition.
* Wed Mar 17 2021 Andreas Stieger - SQLite 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.
* 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.- include changes from 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.
* Improve the built-in documentation for the .dump command in the CLI.
* Mon Mar 15 2021 Dirk Müller - update to 3.35.0:
* 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
* 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.
* 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.
* Thu Jan 21 2021 Andreas Stieger - SQLite 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 (boo#1181261)
* Fix documentation typos
* Fix minor problems in extensions
* Wed Dec 02 2020 Reinhard Max - SQLite 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.
* 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.
* 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.
* Sat Aug 15 2020 Andreas Stieger - SQLite 3.33.0:
* Support for UPDATE FROM following the PostgreSQL syntax
* Increase the maximum size of database files to 281 TB
* Extend 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.
* Add the decimal extension for doing arbitrary-precision decimal arithmetic
* Enhancements to the ieee754 extension for working with IEEE 754 binary64 numbers
* cli: Add four new output modes: \"box\", \"json\", \"markdown\", and \"table\"
* cli: 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
* cli: The \"quote\" output mode honors \".separator\"
* cli: The decimal extension and the ieee754 extension are built-in to the CLI
* multiple query planner improvements
* Sat Jun 20 2020 Andreas Stieger - SQLite 3.32.3:
* Fix Heap Buffer Overflow in multiSelectOrderBy
* Fix Assertion `flags3==pIn3->flags\' failed
* Fix Assertion `pExpr->pAggInfo==pAggInfo\' failed
* Fix Segfault in sqlite3Select
* Fix Use after free in resetAccumulator CVE-2020-13871 boo#1172646
* Fri Jun 05 2020 Paolo Stivanin - SQLite 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
* Tue May 26 2020 Andreas Stieger - SQLite 3.32.1:
* CVE-2020-13435: Malicious SQL statements could have crashed the process that is running SQLite (boo#1172091)
* Sun May 24 2020 Andreas Stieger - SQLite 3.32.0:
* Add support for approximate ANALYZE using the PRAGMA analysis_limit command
* Add the bytecode virtual table
* Add the checksum VFS shim to the set of run-time loadable extensions included in the source tree
* Add the iif() SQL function.
* INSERT and UPDATE statements now always apply column affinity before computing CHECK constraints
* Increase the default upper bound on the number of parameters from 999 to 32766
* Add code for the UINT collating sequence as an optional loadable extension
* multiple enhancements to the CLI
* CVE-2020-13434 boo#1172115: integer overflow in sqlite3_str_vappendf
* CVE-2020-13630 boo#1172234: use-after-free in fts3EvalNextRow
* CVE-2020-13631 boo#1172236: virtual table allowed to be renamed to one of its shadow tables
* CVE-2020-13632 boo#1172240: NULL pointer dereference via crafted matchinfo() query- drop upstreamed patches:
* 04885763c4cd00cb-s390-compatibility.patch
* b20503aaf5b6595a-adapt-FTS-tests-for-big-endian.patch
* Wed Jan 29 2020 Stefan Brüns - Fix a regression on ppc64be and s390x, found by the fuzzing tests, add 04885763c4cd00cb-s390-compatibility.patch.- Adapt some FTS tests to work on big endian archs: b20503aaf5b6595a-adapt-FTS-tests-for-big-endian.patch
* Mon Jan 27 2020 Andreas Stieger - SQLite 3.31.1:
* Revert changes to the data layout for an internal data structure
* Thu Jan 23 2020 Andreas Stieger - SQLite 3.31.0:
* add support for generated columns
* various fixes and improvements- drop upstreamed patches:
* 8a39167bd2-Further-improvements-to-LEFT-JOIN.patch
* fix_dir_exists_on_btrfs.patch
* 7833feecfe-Prevent-SQLite-from-bad-NULL-assumption.patch
* 548082dfab-Improvements-to-the-LEFT-JOIN.patch
* sqlite3-avoid-truncation-error.patch
* Fri Jan 17 2020 Stefan Brüns - Fix regression found when running python-Django/Djano1 testsuite: + 7833feecfe-Prevent-SQLite-from-bad-NULL-assumption.patch + 548082dfab-Improvements-to-the-LEFT-JOIN.patch + 8a39167bd2-Further-improvements-to-LEFT-JOIN.patch- Fix check for existing dirs, triggers when running the testsuite on BTRFS or XFS: + fix_dir_exists_on_btrfs.patch- Fix truncation/bad rounding of timestamps in SQLite strftime function, exposed when running testsuite on i586: + sqlite3-avoid-truncation-error.patch