public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sqlite: Update to version 3390000
Date: Mon, 11 Jul 2022 10:16:51 +0000	[thread overview]
Message-ID: <a896e4c0-86ae-1929-ce3f-b1bbbd339a75@ipfire.org> (raw)
In-Reply-To: <20220710131036.3611221-1-adolf.belka@ipfire.org>

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

Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

> - Update from version 3380500 to 3890000
> - Update of rootfile not required
> - Changelog
>    Release 3.39.0 On 2022-06-25
>     Add (long overdue) support for RIGHT and FULL OUTER JOIN.
>     Add new binary comparison operators IS NOT DISTINCT FROM and IS DISTINCT FROM that are
>      equivalent to IS and IS NOT, respective, for compatibility with PostgreSQL and SQL
>      standards.
>     Add a new return code (value "3") from the sqlite3_vtab_distinct() interface that
>      indicates a query that has both DISTINCT and ORDER BY clauses.
>     Added the sqlite3_db_name() interface.
>     The unix os interface resolves all symbolic links in database filenames to create a
>      canonical name for the database before the file is opened.
>     Defer materializing views until the materialization is actually needed, thus avoiding
>      unnecessary work if the materialization turns out to never be used.
>     The HAVING clause of a SELECT statement is now allowed on any aggregate query, even
>      queries that do not have a GROUP BY clause.
>     Many microoptimizations collectively reduce CPU cycles by about 2.3%.
> 
> 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 4f6d5ad06..a7aa0b499 100644
> --- a/lfs/sqlite
> +++ b/lfs/sqlite
> @@ -24,7 +24,7 @@
>  
>  include Config
>  
> -VER        = 3380500
> +VER        = 3390000
>  
>  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 = 546db2fddfc065ddb5d0f232456a79d6a582cd98acfe7c1c8e0f53311906f70d47d89dfabfdb52c9c261202931b97d84b5fd238f70e6539522e56a57c03036b3
> +$(DL_FILE)_BLAKE2 = 5621aee0468184599f5fea172699ce4db969edb794704c6038009c6fe9fda3613f53de5307e1a5077ca790640f0d7fe82fd7f110c7e1acb0553490da5a5c13f6
>  
>  install : $(TARGET)
>  

      reply	other threads:[~2022-07-11 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10 13:10 Adolf Belka
2022-07-11 10:16 ` 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=a896e4c0-86ae-1929-ce3f-b1bbbd339a75@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