From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: [PATCH] sqlite: Update to version 3400000 Date: Fri, 18 Nov 2022 23:52:10 +0100 Message-ID: <20221118225210.1361959-1-adolf.belka@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9035276386225826759==" List-Id: --===============9035276386225826759== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable - Update from version 3390200 to 3400000 - Update of rootfile not required - Changelog version 3.40.0 On 2022-11-16 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 f= or the next release. Add the recovery extension that might be able to recover some content fr= om 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 b= y the index. Extract the values of expressions contained within expression indexe= s where practical, rather than recomputing the expression. The NOT NULL and IS NULL operators (and their equivalents) avoid loa= ding 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 L= EFT 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 typed= ef instead of "char*". This interface change should be fully backwards compat= ible, 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 defensi= ve mode. Enhancements to the PRAGMA integrity_check statement: Columns in non-STRICT tables with TEXT affinity should not contain n= umeric values. Columns in non-STRICT tables with NUMERIC affinity should not contai= n TEXT values that could be converted into numbers. Verify that the rows of a WITHOUT ROWID table are in the correct ord= er. Enhance the VACUUM INTO statement so that it honors the PRAGMA synchrono= us setting. Enhance the sqlite3_strglob() and sqlite3_strlike() APIs so that they ar= e 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 limit= ing the size of memory allocations. Change the algorithm used by SQLite's built-in pseudo-random number gene= rator (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 cyc= les used on typical workloads. 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 foru= m thread 9b9e4716c0d7bbd1. Use a mutex to protect the PRAGMA temp_store_directory and PRAGMA data_s= tore_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. 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 ca= ses, cause database corruption if the application uses an application-defined= page cache. Enhance SQLITE_DBCONFIG_DEFENSIVE so that it disallows CREATE TRIGGER st= atements if one or more of the statements in the body of the trigger write in= to shadow tables. Fix a possible integer overflow in the size computation for a memory all= ocation in FTS3. Fix a misuse of the sqlite3_set_auxdata() interface in the ICU Extension. Signed-off-by: Adolf Belka --- lfs/sqlite | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lfs/sqlite b/lfs/sqlite index 59233efb6..180b7b30b 100644 --- a/lfs/sqlite +++ b/lfs/sqlite @@ -24,7 +24,7 @@ =20 include Config =20 -VER =3D 3390200 +VER =3D 3400000 =20 THISAPP =3D sqlite-autoconf-$(VER) DL_FILE =3D $(THISAPP).tar.gz @@ -40,7 +40,7 @@ objects =3D $(DL_FILE) =20 $(DL_FILE) =3D $(DL_FROM)/$(DL_FILE) =20 -$(DL_FILE)_BLAKE2 =3D 4f1a2fb0416cd7f3a8af4d6ad699f43f6d814e8d6cc0feaf6eeab6= ab814e8e0e3baaa7bdc175328ce44f59207c7c6266ef2ec79863aba9d14ec163ace15cbf90 +$(DL_FILE)_BLAKE2 =3D b5d03a5117de708681acb6074e63d1d5e6e45a260622b5f8efd31f= 52210097f31e5cf926802aa6e094ec6db0ac677fe62f9b34bf1f50a561efd1e8f110687021 =20 install : $(TARGET) =20 --=20 2.38.1 --===============9035276386225826759==--