public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] sqlite: Update to version 3540000
Date: Thu, 15 Oct 2026 19:23:47 +0200	[thread overview]
Message-ID: <20261015172349.3449498-17-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20261015172349.3449498-1-adolf.belka@ipfire.org>

- Update from version 33530400 to 3540000
- Update of rootfile
- Changelog
3540000
 CLI enhancements:
    CLI prompt strings may contain escape sequences that expand to show state
	information. The initial CLI prompt is now be initialized the values of the
	SQLITE_PS1 and SQLITE_PS2 environment variables, if those variables exist.
    The default CLI prompt has been enhanced to take advantage of the new escape
	sequences described in the previous.
    For columnar output modes, the CLI now shows the column name header by default
	even if the query returns no rows.
    Use the new diskused() extension to implement the ".diskused" dot-command. The
	replaces the separate sqlite3_analyzer utility program, which is now deprecated.
    On unix, the CLI preserves zero bytes when outputing unformatted BLOB values.
    Enhance the .mode command with new options "--rowcount on" and "--titles always".
	The "--titles always" is now the default behavior (see item 3a above). Legacy
	behavior can be restored using "-titles on".
    Enhance the .mode command with the new --ifmt option and --fpfmt option that
	allow the rendering of integer and floating-point values to be more precisely
	controlled using a printf-style format string.
    The -csv command-line option automatically disables display limits, for legacy
	compatibility.
    The default CLI prompt honors the NO_COLOR environment variable.
    The ability to end an SQL command using the line that contains just "go" or "/"
	(for compatibility with SQL Server and Oracle, respectively) is discontinued,
	unless the CLI is compiled with option -DSQLITE_SHELL_LEGACY_COMMAND_TERMINATOR.
Query planner improvements:
    When doing an UPDATE on a table that has expression indexes, do not change the
	expression index if the value being indexed is unchanged.
    Improved optimization of "expr OR TRUE" and "expr OR FALSE".
    Ignore DISTINCT in the SELECT statement on the right-hand side of an IN operator.
    UNION queries with a LIMIT of exactly 1 are now handled faster and with less memory.
The ALTER TABLE command raises an error on any attempt to add, drop, or rename
	columns with the special names "ROWID", "_ROWID_", or "OID".
Add the diskused() SQL function as an optional extension.
Added the %J and %j conversions used to render JSON string literals to the built-in
	printf() and the format() SQL function.
Add the sqlite3_result_str() interface and use it internally to simplify the code.
Add the sqlite3_incomplete() interface and use it as part of the newly enhanced CLI
	prompt string management.
Enhancements to date/time functions:
    Added the "weekday -N" form of the weekday modifier.
    Added the end of modifier.
Use O_TMPFILE when generating temporary files, on systems that support that feature.
Drop support for WindowsXP and earlier Windows versions, including WindowsCE. SQLite
	for Windows now requires Windows Vista (circa 2007) or later.
    Improve performance by using Slim Reader/Writer Locks (SRWLs) to implement
	non-recursive mutexes, instead of CriticalSection, since all supported
	Windows platforms now provide SRWLs.
    Use the -DSQLITE_UWP=1 compile-time option for UWP and WebUI applications.
    To be clear: This changes above only affects SQLite on Windows. Builds for Linux,
	Mac, BSD, and other unix variants are unaffected.
The authorizer callback is now invoked for SQL functions found in the DEFAULT clauses
	of CREATE TABLE statements. This happens both when the CREATE TABLE statement
	is first issued and when the DEFAULT value is actually used, but not when
	reading the schema while opening a database.
Added SQLITE_LIMIT_SCHEMA and SQLITE_LIMIT_TRIGGER_STEPS to the sqlite3_limit() interface.
About 4% faster, as measured by counting CPU cycles in the speedtest1 preformance
	benchmark using valgrind on Linux x64. About 7.5% faster compared to one year
	ago (version 3.51.0). Your mileage may vary depending on workload, build
	options, CPU, compiler, and operating system.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 config/rootfiles/common/sqlite | 2 +-
 lfs/sqlite                     | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/config/rootfiles/common/sqlite b/config/rootfiles/common/sqlite
index 3b430d178..92003f43a 100644
--- a/config/rootfiles/common/sqlite
+++ b/config/rootfiles/common/sqlite
@@ -3,6 +3,6 @@ usr/bin/sqlite3
 #usr/include/sqlite3ext.h
 usr/lib/libsqlite3.so
 usr/lib/libsqlite3.so.0
-usr/lib/libsqlite3.so.3.53.4
+usr/lib/libsqlite3.so.3.54.0
 #usr/lib/pkgconfig/sqlite3.pc
 #usr/share/man/man1/sqlite3.1
diff --git a/lfs/sqlite b/lfs/sqlite
index 6498e84be..b436d2ed0 100644
--- a/lfs/sqlite
+++ b/lfs/sqlite
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 3530400
+VER        = 3540000
 
 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 = 92fa9cf76fa8bba391e75ef2f0599f9730e945dfdff1e2b8031ea90a3e20853230c2981743b12676f21bb30b0b3e629748eef35af2a688ae1073b927b080f40b
+$(DL_FILE)_BLAKE2 = c94a5c32c254ebd08fee5e0ed948e4939973606be8b2ec1c98facb2ddb3f6addd8118a61ac4f63ad9f691605f9eb87d1ca0fded2feb37703bffea06872ee50ff
 
 install : $(TARGET)
 
-- 
2.56.0



  parent reply	other threads:[~2026-10-15 17:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 17:23 [PATCH] core206: Ship glib Adolf Belka
2026-10-15 17:23 ` [PATCH] core206: Ship groff Adolf Belka
2026-10-15 17:23 ` [PATCH] core206: Ship harfbuzz Adolf Belka
2026-10-15 17:23 ` [PATCH] core206: Ship hwdata Adolf Belka
2026-10-15 17:23 ` [PATCH] core206: Ship openssh Adolf Belka
2026-10-15 17:23 ` [PATCH] core206: Ship openvpn Adolf Belka
2026-10-15 17:23 ` [PATCH] core206: Ship sqlite Adolf Belka
2026-10-15 17:23 ` [PATCH] faad2: Update to version 2.11.4 Adolf Belka
2026-10-15 17:23 ` [PATCH] ffmpeg: Update to version 9.0.2 Adolf Belka
2026-10-15 17:23 ` [PATCH] glib: Update to version 2.90.1 Adolf Belka
2026-10-15 17:23 ` [PATCH] groff: Update to version 1.24.2 Adolf Belka
2026-10-15 17:23 ` [PATCH] harfbuzz: Update to version 14.6.0 Adolf Belka
2026-10-15 17:23 ` [PATCH] hwdata: Update to version 0.412 Adolf Belka
2026-10-15 17:23 ` [PATCH] openssh: Update to version 10.6p1 Adolf Belka
2026-10-15 17:23 ` [PATCH] openvpn: Update to version 2.7.8 Adolf Belka
2026-10-15 17:23 ` [PATCH] shairport-sync: Update to version 5.6 Adolf Belka
2026-10-15 17:23 ` Adolf Belka [this message]
2026-10-15 17:23 ` [PATCH] tmux: Update to version 3.8 Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261015172349.3449498-17-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox