[Bug 264974] databases/sqlite3: Update to 3.39
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 264974] databases/sqlite3: Update to 3.39"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 07 Jul 2022 05:35:51 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264974
--- Comment #6 from commit-hook@FreeBSD.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=5bf2947fce86388fd612492f980540c07d41f0b2
commit 5bf2947fce86388fd612492f980540c07d41f0b2
Author: Pavel Volkov <pavelivolkov@gmail.com>
AuthorDate: 2022-07-05 05:52:02 +0000
Commit: Fernando ApesteguĂa <fernape@FreeBSD.org>
CommitDate: 2022-07-07 05:32:47 +0000
databases/sqlite3: Update to 3.39
ChangeLog: https://www.sqlite.org/releaselog/3_39_0.html
* 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%.
PR: 264974
Reported by: pavelivolkov@gmail.com (maintainer)
databases/sqlite3/Makefile | 6 +++---
databases/sqlite3/distinfo | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
--
You are receiving this mail because:
You are the assignee for the bug.