Re: [PATCH] sqlite: Update to version 3400000

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 4967 bytes --]

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 18 Nov 2022, at 22:52, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> - 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 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 the 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.
> 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.
> 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.
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> 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 @@
> 
> include Config
> 
> -VER        = 3390200
> +VER        = 3400000
> 
> THISAPP    = sqlite-autoconf-$(VER)
> DL_FILE    = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_BLAKE2 = 4f1a2fb0416cd7f3a8af4d6ad699f43f6d814e8d6cc0feaf6eeab6ab814e8e0e3baaa7bdc175328ce44f59207c7c6266ef2ec79863aba9d14ec163ace15cbf90
> +$(DL_FILE)_BLAKE2 = b5d03a5117de708681acb6074e63d1d5e6e45a260622b5f8efd31f52210097f31e5cf926802aa6e094ec6db0ac677fe62f9b34bf1f50a561efd1e8f110687021
> 
> install : $(TARGET)
> 
> -- 
> 2.38.1
>