From 18657a960e125336f704ea058e25c27bd3900dcb Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 5 May 2024 19:28:19 +0200 Subject: Adding upstream version 3.40.1. Signed-off-by: Daniel Baumann --- www/releaselog/3_39_4.html | 207 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 207 insertions(+) create mode 100644 www/releaselog/3_39_4.html (limited to 'www/releaselog/3_39_4.html') diff --git a/www/releaselog/3_39_4.html b/www/releaselog/3_39_4.html new file mode 100644 index 0000000..248f128 --- /dev/null +++ b/www/releaselog/3_39_4.html @@ -0,0 +1,207 @@ + + + + + +SQLite Release 3.39.4 On 2022-09-29 + + + +
+ + + +
+
+Small. Fast. Reliable.
Choose any three. +
+
+ +
+ +
+
+ + + +
+
+
+ +

SQLite Release 3.39.4 On 2022-09-29

Changes in version 3.39.0 (2022-06-25):

+

    +
  1. Add (long overdue) support for RIGHT and FULL OUTER JOIN. +
  2. 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. +
  3. 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. +
  4. Added the sqlite3_db_name() interface. +
  5. The unix os interface resolves all symbolic links in database + filenames to create a canonical name for the database before the + file is opened. + If the SQLITE_OPEN_NOFOLLOW flag is used with sqlite3_open_v2() + or similar, the open will fail if any element of the path is a + symbolic link. +
  6. Defer materializing views until the materialization + is actually needed, thus avoiding unnecessary work if the materialization turns + out to never be used. +
  7. The HAVING clause of a SELECT statement is now allowed on any aggregate query, + even queries that do not have a GROUP BY clause. +
  8. Many microoptimizations collectively reduce CPU cycles by about 2.3%. +
+

Additional changes in version 3.39.1 (2022-07-13):

+

    +
  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. + forum post 174afeae5734d42d. +
  2. Fix some harmless compiler warnings. +
  3. 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. +
  4. Fix a long-standing problem in FTS3 that can only arise when compiled with + the SQLITE_ENABLE_FTS3_PARENTHESIS compile-time option. +
  5. 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. +
  6. 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. +
  7. Enhance the sqlite_stmt virtual table so that it buffers all of its output. +
+

Additional changes in version 3.39.2 (2022-07-21):

+

    +
  1. Fix a performance regression in the query planner associated with rearranging + the order of FROM clause terms in the presences of a LEFT JOIN. +
  2. Apply fixes for CVE-2022-35737, Chromium bugs 1343348 and 1345947, + forum post 3607259d3c, and + other minor problems discovered by internal testing. +
+

Additional changes in version 3.39.3 (2022-09-05):

+

    +
  1. 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. +
  2. 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. +
  3. Other bug and warning fixes. See the + timeline + for details. +
+

Additional changes in version 3.39.4 (2022-09-29):

+

    +
  1. Fix the build on Windows so that it works with -DSQLITE_OMIT_AUTOINIT +
  2. 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. +
  3. 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. +
  4. Fix a possible integer overflow in the size computation for a memory allocation + in FTS3. +
  5. Fix a misuse of the sqlite3_set_auxdata() interface in the + ICU Extension. +

    Hashes: +

  6. SQLITE_SOURCE_ID: 2022-09-29 15:55:41 a29f9949895322123f7c38fbe94c649a9d6e6c9cd0c3b41c96d694552f26b309 +
  7. SHA3-256 for sqlite3.c: f65082298127e2ddae6539beb94f5204b591df64ba2c7da83c7d0faffd6959d8 + +

+ +

A complete list of SQLite releases + in a single page and a chronology are both also available. + A detailed history of every + check-in is available at + + SQLite version control site.

+ + -- cgit v1.2.3