From patchwork Fri Nov 10 10:59:05 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Adolf Belka X-Patchwork-Id: 7329 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 (secp384r1) client-signature ECDSA (secp384r1)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4SRbS43T7Lz3wvm for ; Fri, 10 Nov 2023 10:59:32 +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 (secp384r1) client-signature ECDSA (secp384r1)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4SRbRs5x9Vz2y1; Fri, 10 Nov 2023 10:59:21 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4SRbRs2hcxz33gD; Fri, 10 Nov 2023 10:59:21 +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 (secp384r1) client-signature ECDSA (secp384r1)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4SRbRp4YV8z2xKQ for ; Fri, 10 Nov 2023 10:59:18 +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 (secp384r1) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4SRbRp36hMzw9; Fri, 10 Nov 2023 10:59:18 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1699613958; 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: in-reply-to:in-reply-to:references:references; bh=QyHnNp0YXJ37OzqzlAkU5vgYW7ZmV6NMHAdEqS0Zino=; b=5GMoi/OlPNyWmr3GKMV5YO/xGjrMqAZOfxbKIVedqvv5X6Dz57BxH6vEMgl2hs0o+9nI3D jjz3tr2FykfIe7Bg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1699613958; 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: in-reply-to:in-reply-to:references:references; bh=QyHnNp0YXJ37OzqzlAkU5vgYW7ZmV6NMHAdEqS0Zino=; b=IsbB4pKWeC2+B5+nOyRun9svNGze7LzOjQZX3vMI8Lg7inUkw1GQN+heEJ8dyRh+vMeVRB 2WPacHF2TDv7AaF/rdDzc7b88AeyulnzDEXRjCPMfy1do1vribrWxpgQQ9habSPfGVH/Ip zNqitJhJehL3zAr1rQ93mM+F/YZq3W2B/RYcqLDdZ+feKyMtO76m4NNSc0rh2c+EVE+lQX YdN+PS5GhK7LgBHcWrRe/lMos2gR26R47PCihMaZYT/F79hqYu/ii4BTQZ3WiisFNQLNvk m1UtqxuSGtJGc4LoqO8inNXdG7yTYWXr785ppJ/H6Uu9OB4cf9z7amNf6mF+Rg== From: Adolf Belka To: development@lists.ipfire.org Subject: [PATCH] sqlite: Update to version 3440000 Date: Fri, 10 Nov 2023 11:59:05 +0100 Message-ID: <20231110105910.11113-8-adolf.belka@ipfire.org> In-Reply-To: <20231110105910.11113-1-adolf.belka@ipfire.org> References: <20231110105910.11113-1-adolf.belka@ipfire.org> MIME-Version: 1.0 Message-ID-Hash: 2RUP5GHXIQQHIK2MVINUE33YAHEJCEXE X-Message-ID-Hash: 2RUP5GHXIQQHIK2MVINUE33YAHEJCEXE X-MailFrom: adolf.belka@ipfire.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.8 Precedence: list List-Id: IPFire development talk Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: - Update from version 3430000 to 3440000 - Update of rootfile not required - Changelog 3.44.0 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(). Add support for the concat() and concat_ws() scalar SQL functions, compatible with PostgreSQL, SQLServer, and MySQL. Add support for the string_agg() aggregate SQL function, compatible with PostgreSQL and SQLServer. New conversion letters on the strftime() SQL function: %e %F %I %k %l %p %P %R %T %u Add new C-language APIs: sqlite3_get_clientdata() and sqlite3_set_clientdata(). 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. 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. 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. 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. 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. 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 Query planner optimizations: 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. 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. 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. 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. 3.43.2 Fix a couple of obscure UAF errors and an obscure memory leak. Omit the use of the sprintf() function from the standard library in the CLI, as this now generates warnings on some platforms. Avoid conversion of a double into unsigned long long integer, as some platforms do not do such conversions correctly. 3.43.1 Fix a regression in the way that the sum(), avg(), and total() aggregate functions handle infinities. Fix a bug in the json_array_length() function that occurs when the argument comes directly from json_remove(). Fix the omit-unused-subquery-columns optimization (introduced in version 3.42.0) so that it works correctly if the subquery is a compound where one arm is DISTINCT and the other is not. Other minor fixes. Signed-off-by: Adolf Belka --- lfs/sqlite | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lfs/sqlite b/lfs/sqlite index 01477e47d..4d44d6fda 100644 --- a/lfs/sqlite +++ b/lfs/sqlite @@ -24,7 +24,7 @@ include Config -VER = 3430000 +VER = 3440000 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 = dc5a5df76ffe86eb61438031ef3893fbe412f7c7607826dd032293ced06b2f76dfb5f6b85ba80e857069ea4244a3ec222f3f247faec192778c3ecfcc810faa07 +$(DL_FILE)_BLAKE2 = adadcf5b17aec2d6727536d9c388b76ceacfb73d51c905ed906cc09a48806091624f9bb688de8b995e09b7cad97a21deb1ac91a17c4e60f658870d4ae85d5358 install : $(TARGET)