From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sqlite: Update to version 3380300
Date: Fri, 29 Apr 2022 18:35:27 +0000 [thread overview]
Message-ID: <9b203de2-9b2b-96f1-3673-deef279122eb@ipfire.org> (raw)
In-Reply-To: <20220428111425.3578089-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2716 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> - Update from version 3380000 to 3380300
> - Update of rootfile not required
> - Changelog
> 3.38.3 (2022-04-27):
> Fix a case of the query planner be overly aggressive with optimizing
> automatic-index and Bloom-filter construction, using inappropriate ON clause
> terms to restrict the size of the automatic-index or Bloom filter, and
> resulting in missing rows in the output. Forum thread 0d3200f4f3bcd3a3.
> Other minor patches. See the timeline for details.
> 3.38.2 (2022-03-26):
> Fix a user-discovered problem with the new Bloom filter optimization that
> might cause an incorrect answer when doing a LEFT JOIN with a WHERE clause
> constraint that says that one of the columns on the right table of the LEFT
> JOIN is NULL. See forum thread 031e262a89b6a9d2.
> Other minor patches. See the timeline for details.
> 3.38.1 (2022-03-12):
> Fix problems with the new Bloom filter optimization that might cause some
> obscure queries to get an incorrect answer.
> Fix the localtime modifier of the date and time functions so that it
> preserves fractional seconds.
> Fix the sqlite_offset SQL function so that it works correctly even in corner
> cases such as when the argument is a virtual column or the column of a view.
> Fix row value IN operator constraints on virtual tables so that they work
> correctly even if the virtual table implementation relies on bytecode to
> filter rows that do not satisfy the constraint.
> Other minor fixes to assert() statements, test cases, and documentation. See
> the source code timeline for details.
>
> 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 7986b2ce5..076943280 100644
> --- a/lfs/sqlite
> +++ b/lfs/sqlite
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 3380000
> +VER = 3380300
>
> 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 = 0b4eff73e9a7b317d080439c9e74b47a09e8809d4629a2ee31d410df2ce626d6bd6e9c5bdc5d0d4f104d981ee7b3a8a31bf2d7153932ad866f5e876c1608f6da
> +$(DL_FILE)_BLAKE2 = 35271246a27597ce88b4eaa1ff483b42421371737b5fe357eb6d2ad1d9c543b2d60341f7ee63f7dc95e374f61c539a607472b53881027c843b0da07704dd200f
>
> install : $(TARGET)
>
prev parent reply other threads:[~2022-04-29 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 11:14 Adolf Belka
2022-04-29 18:35 ` 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=9b203de2-9b2b-96f1-3673-deef279122eb@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