From patchwork Fri Nov 18 22:52:10 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Adolf Belka X-Patchwork-Id: 6139 Return-Path: Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4NDX9C2GW9z3wgd for ; Fri, 18 Nov 2022 22:52:15 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4NDX9B4hy8z1YZ; Fri, 18 Nov 2022 22:52:14 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4NDX9B49rTz2yvq; Fri, 18 Nov 2022 22:52:14 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4NDX993YsGz2xRr for ; Fri, 18 Nov 2022 22:52:13 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4NDX985P6Mzdk; Fri, 18 Nov 2022 22:52:12 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1668811932; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=utEbXo9xY0Tx3paztOetW5w6CneM/z2/cmHA0UoMhCE=; b=1qL/TuNm9jznnvEI62sYvWk10G9rJremmwk21c+6ui3oTwXVaO/FlcT8ZTKL6FzWeuNuL/ xNnCMveYXXG1gWDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1668811932; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=utEbXo9xY0Tx3paztOetW5w6CneM/z2/cmHA0UoMhCE=; b=iLrOpASyvIh6xVLxZ1Y4dH7xJthju2gaZziv3mAbj+T5pN7KGLHocdZw3db1kevAr50J7p WiBNnLphQtuuK5+PLHZU8eucXRehVgM8qCkSskin2fp9sxmWD7+eVUWE3EwQPOX/YzqzCt n6dgRhpGGeSWFn/xl5o8lE/mxNcYjT3KMTRF/QERuNwPkeocmCiOafRU/f6vrOhOv+85iQ zXZRpW0N9+dlE4RyaaogGmgFJ/Z0DTrssv2v21H0upF6q2k6I3HbwQ+gKeq7gVWd3UnEFT ftvMWN4SacYiwMvdYxzv55jAR2GiszYqZdj+mhLwedKlT5ltMqRo6cubfAwjTA== 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 X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: development-bounces@lists.ipfire.org Sender: "Development" - 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 Reviewed-by: Michael Tremer --- 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)