From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sqlite: Update to version 3390200
Date: Sun, 11 Sep 2022 13:59:43 +0000 [thread overview]
Message-ID: <9008153d-c2f9-2eb7-75da-409ce0a650af@ipfire.org> (raw)
In-Reply-To: <20220824075115.3040-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2560 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> - Update from version 3390000 to 3390200
> - Update of rootfile not required
> - Changelog
> version 3.39.2 (2022-07-21):
> Fix a performance regression in the query planner associated with rearranging
> the order of FROM clause terms in the presences of a LEFT JOIN.
> Apply fixes for CVE-2022-35737, Chromium bugs 1343348 and 1345947, forum post
> 3607259d3c, and other minor problems discovered by internal testing.
> version 3.39.1 (2022-07-13):
> Fix an incorrect result from a query that uses a view that contains a
> compound SELECT in which only one arm contains a RIGHT JOIN and where the
> view is not the first FROM clause term of the query that contains the view.
> forum post 174afeae5734d42d.
> Fix some harmless compiler warnings.
> Fix a long-standing problem with ALTER TABLE RENAME that can only arise if
> the sqlite3_limit(SQLITE_LIMIT_SQL_LENGTH) is set to a very small value.
> Fix a long-standing problem in FTS3 that can only arise when compiled with
> the SQLITE_ENABLE_FTS3_PARENTHESIS compile-time option.
> Fix the build so that is works when the SQLITE_DEBUG and
> SQLITE_OMIT_WINDOWFUNC compile-time options are both provided at the same time.
> Fix the initial-prefix optimization for the REGEXP extension so that it works
> correctly even if the prefix contains characters that require a 3-byte UTF8
> encoding.
> Enhance the sqlite_stmt virtual table so that it buffers all of its output.
>
> 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 a7aa0b499..59233efb6 100644
> --- a/lfs/sqlite
> +++ b/lfs/sqlite
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 3390000
> +VER = 3390200
>
> 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 = 5621aee0468184599f5fea172699ce4db969edb794704c6038009c6fe9fda3613f53de5307e1a5077ca790640f0d7fe82fd7f110c7e1acb0553490da5a5c13f6
> +$(DL_FILE)_BLAKE2 = 4f1a2fb0416cd7f3a8af4d6ad699f43f6d814e8d6cc0feaf6eeab6ab814e8e0e3baaa7bdc175328ce44f59207c7c6266ef2ec79863aba9d14ec163ace15cbf90
>
> install : $(TARGET)
>
prev parent reply other threads:[~2022-09-11 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 7:51 Adolf Belka
2022-09-11 13:59 ` Peter Müller [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=9008153d-c2f9-2eb7-75da-409ce0a650af@ipfire.org \
--to=peter.mueller@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