Log message:
sqlite3: updated to 3.38.5

3.38.5 (2022-05-06):

Fix a blunder in the CLI of the 3.38.4 release.

Log message:
sqlite3: updated to 3.38.4

3.38.4 (2022-05-04):

Fix a byte-code problem in the Bloom filter pull-down optimization added by \ 
release 3.38.0 in which an error in the byte code causes the byte code engine to \ 
enter an infinite loop when the pull-down optimization encounters a NULL key.

Log message:
sqlite3: updated to 3.38.3

changes in version 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.

Log message:
sqlite3: updated to 3.38.2

Additional changes in version 3.38.2 (2022-03-26):

Fix another 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.

Log message:
sqlite3: updated to 3.38.1

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.

Log message:
sqlite3: updated to 3.38.0

SQLite Release 3.38.0 On 2022-02-22

Added the -> and ->> operators for easier processing of JSON. The new \ 
operators are compatible with MySQL and PostgreSQL.
The JSON functions are now built-ins. It is no longer necessary to use the \ 
-DSQLITE_ENABLE_JSON1 compile-time option to enable JSON support. JSON is on by \ 
default. Disable the JSON interface using the new -DSQLITE_OMIT_JSON \ 
compile-time option.
Enhancements to date and time functions:
Added the unixepoch() function.
Added the auto modifier and the julianday modifier.
Rename the printf() SQL function to format() for better compatibility. The \ 
original printf() name is retained as an alias for backwards compatibility.
Added the sqlite3_error_offset() interface, which can sometimes help to localize \ 
an SQL error to a specific character in the input SQL text, so that applications \ 
can provide better error messages.
Enhanced the interface to virtual tables as follows:
Added the sqlite3_vtab_distinct() interface.
Added the sqlite3_vtab_rhs_value() interface.
Added new operator types SQLITE_INDEX_CONSTRAINT_LIMIT and \ 
SQLITE_INDEX_CONSTRAINT_OFFSET.
Added the sqlite3_vtab_in() interface (and related) to enable a virtual table to \ 
process IN operator constraints all at once, rather than processing each value \ 
of the right-hand side of the IN operator separately.
CLI enhancements:
Columnar output modes are enhanced to correctly handle tabs and newlines \ 
embedded in text.
Added options like "--wrap N", "--wordwrap on", and \ 
"--quote" to the columnar output modes.
Added the .mode qbox alias.
The .import command automatically disambiguates column names.
Use the new sqlite3_error_offset() interface to provide better error messages.
Query planner enhancements:
Use a Bloom filter to speed up large analytic queries.
Use a balanced merge tree to evaluate UNION or UNION ALL compound SELECT \ 
statements that have an ORDER BY clause.
The ALTER TABLE statement is changed to silently ignores entries in the \ 
sqlite_schema table that do not parse when PRAGMA writable_schema=ON.

Log message:
sqlite3: updated to 3.37.2

Changes in version 3.37.2:

Fix a bug introduced in version 3.35.0 (2021-03-12) that can cause database \ 
corruption if a SAVEPOINT is rolled back while in PRAGMA temp_store=MEMORY mode, \ 
and other changes are made, and then the outer transaction commits. Check-in \ 
73c2b50211d3ae26
Fix a long-standing problem with ON DELETE CASCADE and ON UPDATE CASCADE in \ 
which a cache of the bytecode used to implement the cascading change was not \ 
being reset following a local DDL change. Check-in 5232c9777fe4fb13.
Other minor fixes that should not impact production builds.

Log message:
sqlite3: updated to 3.37.1

version 3.37.1

Fix a bug introduced by the UPSERT enhancements of version 3.35.0 that can cause \ 
incorrect byte-code to be generated for some obscure but valid SQL, possibly \ 
resulting in a NULL-pointer dereference.
Fix an OOB read that can occur in FTS5 when reading corrupt database files.
Improved robustness of the --safe option in the CLI.
Other minor fixes to assert() statements and test cases.

Log message:
sqlite3: updated to 3.37.0

SQLite Release 3.37.0 On 2021-11-27

STRICT tables provide a prescriptive style of data type management, for \ 
developers who prefer that kind of thing.
When adding columns that contain a CHECK constraint or a generated column \ 
containing a NOT NULL constraint, the ALTER TABLE ADD COLUMN now checks new \ 
constraints against preexisting rows in the database and will only proceed if no \ 
constraints are violated.
Added the PRAGMA table_list statement.
CLI enhancements:
Add the .connection command, allowing the CLI to keep multiple database \ 
connections open at the same time.
Add the --safe command-line option that disables dot-commands and SQL statements \ 
that might cause side-effects that extend beyond the single database file named \ 
on the command-line.
Performance improvements when reading SQL statements that span many lines.
Added the sqlite3_autovacuum_pages() interface.
The sqlite3_deserialize() does not and has never worked for the TEMP database. \ 
That limitation is now noted in the documentation.
The query planner now omits ORDER BY clauses on subqueries and views if removing \ 
those clauses does not change the semantics of the query.
The generate_series table-valued function extension is modified so that the \ 
first parameter ("START") is now required. This is done as a way to \ 
demonstrate how to write table-valued functions with required parameters. The \ 
legacy behavior is available using the -DZERO_ARGUMENT_GENERATE_SERIES \ 
compile-time option.
Added new sqlite3_changes64() and sqlite3_total_changes64() interfaces.
Added the SQLITE_OPEN_EXRESCODE flag option to sqlite3_open_v2().
Use less memory to hold the database schema.

Log message:
archivers: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Could not be committed due to merge conflict:
devel/py-traitlets/distinfo

The following distfiles were unfetchable (note: some may be only fetched
conditionally):

./devel/pvs/distinfo pvs-3.2-solaris.tgz
./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip