[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk 2022-11-17T06:20:44Z 2022-11-17T06:20:44Z adam adam@pkgsrc.org 2022-11-17T06:20:44Z urn:sha1:bc73f172a3bf74642442304c27846fa18a35072a 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. 2022-10-03T12:27:52Z adam adam@pkgsrc.org 2022-10-03T12:27:52Z urn:sha1:4dc4661e4020258bb57b3652da60dbc9e34ece09 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. 2022-09-06T18:59:11Z adam adam@pkgsrc.org 2022-09-06T18:59:11Z urn:sha1:0abe6cf85caaea0cc46d82d44fd18a9dbe9db8c7 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. 2022-07-22T07:05:55Z adam adam@pkgsrc.org 2022-07-22T07:05:55Z urn:sha1:7da6336394dfd5664aa7887a299dc969b425b1c8 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. 2022-07-14T08:05:51Z adam adam@pkgsrc.org 2022-07-14T08:05:51Z urn:sha1:a589a81181ebd68b2bcfc19552cc377ada1b73b6 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. 2022-07-01T17:49:39Z adam adam@pkgsrc.org 2022-07-01T17:49:39Z urn:sha1:ff04922bb8c7e4c6b3aed7e22dbbd604df3ae4eb 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%. 2022-05-08T08:10:26Z adam adam@pkgsrc.org 2022-05-08T08:10:26Z urn:sha1:a68aa546556f28322e7597b3fb3616b7a42dc8ec 3.38.5 (2022-05-06): Fix a blunder in the CLI of the 3.38.4 release. 2022-05-05T17:26:41Z adam adam@pkgsrc.org 2022-05-05T17:26:41Z urn:sha1:d762207c03b7802957b7a1ed65c6403249fb6bb5 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. 2022-04-27T17:12:17Z adam adam@pkgsrc.org 2022-04-27T17:12:17Z urn:sha1:80deb22c5383b1a1589bfc5e968d2d69c6ec2929 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. 2022-03-28T19:38:27Z adam adam@pkgsrc.org 2022-03-28T19:38:27Z urn:sha1:dabf533eacf47346f0dfa86478352db3ac35a15b 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.