From 63847496f14c813a5d80efd5b7de0f1294ffe1e3 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 13 Apr 2024 16:07:11 +0200 Subject: Adding upstream version 3.45.1. Signed-off-by: Daniel Baumann --- www/releaselog/3_44_2.html | 191 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 191 insertions(+) create mode 100644 www/releaselog/3_44_2.html (limited to 'www/releaselog/3_44_2.html') diff --git a/www/releaselog/3_44_2.html b/www/releaselog/3_44_2.html new file mode 100644 index 0000000..1e173f5 --- /dev/null +++ b/www/releaselog/3_44_2.html @@ -0,0 +1,191 @@ + + + + + +SQLite Release 3.44.2 On 2023-11-24 + + + +
+ + + +
+
+Small. Fast. Reliable.
Choose any three. +
+
+ +
+ +
+
+ + + +
+
+
+ +

SQLite Release 3.44.2 On 2023-11-24

Prior changes from version 3.44.0 (2023-11-01):

+

    +
  1. 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(). +
  2. Add support for the concat() and concat_ws() scalar SQL functions, + compatible with PostgreSQL, SQLServer, and MySQL. +
  3. Add support for the string_agg() aggregate SQL function, compatible + with PostgreSQL and SQLServer. +
  4. New conversion letters on the strftime() SQL function: %e %F %I %k %l %p %P %R %T %u +
  5. Add new C-language APIs: sqlite3_get_clientdata() and sqlite3_set_clientdata(). +
  6. 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. +
  7. 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. +
  8. 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. +
  9. 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. +
  10. 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. +
  11. 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 +
  12. Query planner optimizations: +
      +
    1. 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. +
    2. 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. +
    +
  13. 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. +
  14. 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. +
+

Prior changes from version 3.44.1 (2023-11-22):

+

    +
  1. 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. +
  2. Other obscure bug fixes. +
+

Changes in this specific patch release, version 3.44.2 (2023-11-24):

+

    +
  1. Fix a mistake in the CLI that was introduced by the fix (item 15 above) in 3.44.1. +
  2. Fix a problem in FTS5 that was discovered during internal fuzz testing only + minutes after the 3.44.1 release was tagged. +
  3. Fix incomplete assert() statements that the fuzzer discovered the day after + the previous release. +
  4. Fix a couple of harmless compiler warnings that appeared in debug builds with GCC 16. +

    Hashes: +

  5. SQLITE_SOURCE_ID: 2023-11-24 11:41:44 ebead0e7230cd33bcec9f95d2183069565b9e709bf745c9b5db65cc0cbf92c0f +
  6. SHA3-256 for sqlite3.c: bd70b012e2d1b3efa132d905224cd0ab476a69b892f8c6b21135756ec7ffbb13 + +

+ +

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