public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] sqlite: Update to version 3460100
Date: Wed, 14 Aug 2024 18:22:44 +0200	[thread overview]
Message-ID: <20240814162244.3428257-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20240814162244.3428257-1-adolf.belka@ipfire.org>

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

- Update from version 3460000 to 3460100
- Update of rootfile not required
- Changelog
    3460100
	Improved robustness while parsing the tokenize= arguments in FTS5. Forum post
	 171bcc2bcd.
	Enhancements to covering index prediction in the query planner. Add early
	 detection of over-prediction of covering indexes so that sqlite3_prepare() will
	 return an error rather than just generate bad bytecode. Forum post
	 e60e4c295d22f8ce.
	Do not let the number of terms on a VALUES clause be limited by
	 SQLITE_LIMIT_COMPOUND_SELECT, even if the VALUES clause contains elements that
	 appear to be variables due to double-quoted string literals.
	Fix the window function version of group_concat() so that it returns an empty
	 string if it has one or more empty string inputs.
	In FTS5 secure-delete mode, fix false-positive integrity-check reports about
	 corrupt indexes.
	Syntax errors in ALTER TABLE should always return SQLITE_ERROR. In some cases,
	 they were formerly returning SQLITE_INTERNAL.
	JavaScript/WASM:
	    Fix a corruption-causing bug in the JavaScript "opfs" VFS.
	    Work around a couple of browser-specific OPFS quirks.
	Other minor fixes.

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 d001a5f49..6998ae087 100644
--- a/lfs/sqlite
+++ b/lfs/sqlite
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 3460000
+VER        = 3460100
 
 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 = 2f484823b84ab758e21960ac6b730cefa62c26f7ccf5344299a26e6f559d0e02cfd4cff5f5921effdee6e2e49d2ab36b1f91cffdd8599bc2189efab44bf4b197
+$(DL_FILE)_BLAKE2 = b84bc7f6cbe2f1a4894b725d68ebdc58eebc312581fd27e74a75086e834b2b2f4ff09b907e193d8eaf78d9829149de8d9ea587cf650849fe4d3fc84db64ddfad
 
 install : $(TARGET)
 
-- 
2.46.0


      reply	other threads:[~2024-08-14 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 16:22 [PATCH] intel-microcode: Update to version 20240813 Adolf Belka
2024-08-14 16:22 ` Adolf Belka [this message]

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=20240814162244.3428257-2-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