CVS log for src/external/public-domain/sqlite/dist/sqlite3.rc

Up to [cvs.NetBSD.org] / src / external / public-domain / sqlite / dist

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: SQLITE, MAIN

Import 3.43.0 (last was 3.26.0)

2023-08-24 (3.43.0)
Add support for Contentless-Delete FTS5 Indexes. This is a variety
of FTS5 full-text search index that omits storing the content that
is being indexed while also allowing records to be deleted.
Enhancements to the date and time functions:
Added new time shift modifiers of the form ±YYYY-MM-DD HH:MM:SS.SSS.
Added the timediff() SQL function.
Added the octet_length(X) SQL function.
Added the sqlite3_stmt_explain() API.
Query planner enhancements:
Generalize the LEFT JOIN strength reduction optimization so that
it works for RIGHT and FULL JOINs as well. Rename it to OUTER JOIN
strength reduction.
Enhance the theorem prover in the OUTER JOIN strength reduction
optimization so that it returns fewer false-negatives.
Enhancements to the decimal extension:
New function decimal_pow2(N) returns the N-th power of 2 for integer
N between -20000 and +20000.
New function decimal_exp(X) works like decimal(X) except that it
returns the result in exponential notation - with a "e+NN" at the
end.
If X is a floating-point value, then the decimal(X) function now
does a full expansion of that value into its exact decimal equivalent.
Performance enhancements to JSON processing results in a 2x
performance improvement for some kinds of processing on large JSON
strings.
New makefile target "verify-source" checks to ensure that there
are no unintentional changes in the source tree. (Works for canonical
source code only - not for precompiled amalgamation tarballs.)
Added the SQLITE_USE_SEH compile-time option that enables Structured
Exception Handling on Windows while working with the memory-mapped
shm file that is part of WAL mode processing. This option is enabled
by default when building on Windows using Makefile.msc.
The VFS for unix now assumes that the nanosleep() system call is
available unless compiled with -DHAVE_NANOSLEEP=0.
Hashes:
SQLITE_SOURCE_ID: 2023-08-24 12:36:59
0f80b798b3f4b81a7bb4233c58294edd0f1156f36b6ecf5ab8e83631d468778c
SHA3-256 for sqlite3.c:
a6fc5379891d77b69a7d324cd24a437307af66cfdc3fef5dfceec3c82c8d4078

2023-05-16 (3.42.0)
Add the FTS5 secure-delete command. This option causes all forensic
traces to be removed from the FTS5 inverted index when content is
deleted.
Enhance the JSON SQL functions to support JSON5 extensions.
The SQLITE_CONFIG_LOG and SQLITE_CONFIG_PCACHE_HDRSZ calls to
sqlite3_config() are now allowed to occur after sqlite3_initialize().
New sqlite3_db_config() options: SQLITE_DBCONFIG_STMT_SCANSTATUS
and SQLITE_DBCONFIG_REVERSE_SCANORDER.
Query planner improvements:
Enable the "count-of-view" optimization by default.
Avoid computing unused columns in subqueries.
Improvements to the push-down optimization.
Enhancements to the CLI:
Add the --unsafe-testing command-line option. Without this option,
some dot-commands (ex: ".testctrl") are now disabled because those
commands that are intended for testing only and can cause malfunctions
misused.
Allow commands ".log on" and ".log off", even in --safe mode.
"--" as a command-line argument means all subsequent arguments that
start with "-" are interpreted as normal non-option argument.
Magic parameters ":inf" and ":nan" bind to floating point literals
Infinity and NaN, respectively.
The --utf8 command-line option omits all translation to or from
MBCS on the Windows console for interactive sessions, and sets the
console code page for UTF-8 I/O during such sessions. The --utf8
option is a no-op on all other platforms.
Add the ability for application-defined SQL functions to have the
same name as join keywords: CROSS, FULL, INNER, LEFT, NATURAL,
OUTER, or RIGHT.
Enhancements to PRAGMA integrity_check:
Detect and raise an error when a NaN value is stored in a NOT NULL
column.
Improved error message output identifies the root page of a b-tree
when an error is found within a b-tree.
Allow the session extension to be configured to capture changes
from tables that lack an explicit ROWID.
Added the subsecond modifier to the date and time functions.
Negative values passed into sqlite3_sleep() are henceforth interpreted
as 0.
The maximum recursion depth for JSON arrays and objects is lowered
from 2000 to 1000.
Extended the built-in printf() function so the comma option now
works with floating-point conversions in addition to integer
conversions.
Miscellaneous bug fixes and performance optimizations
Hashes:
SQLITE_SOURCE_ID: 2023-05-16 12:36:15
831d0fb2836b71c9bc51067c49fee4b8f18047814f2ff22d817d25195cf350b0
SHA3-256 for sqlite3.c:
6aa3fadf000000625353bbaa1e83af114c40c240a0aa5a2c1c2aabcfc28d4f92

2023-03-22 (3.41.2)
Multiple fixes for reads past the end of memory buffers (NB: reads
not writes) in the following circumstances:
When processing a corrupt database file using the non-standard
SQLITE_ENABLE_STAT4 compile-time option.
In the CLI when the sqlite3_error_offset() routine returns an
out-of-range value (see also the fix to sqlite3_error_offset()
below).
In the recovery extension.
In FTS3 when processing a corrupt database file.
Fix the sqlite3_error_offset() so that it does not return out-of-range
values when reporting errors associated with generated columns.
Multiple fixes in the query optimizer for problems that cause
incorrect results for bizarre, fuzzer-generated queries.
Increase the size of the reference counter in the page cache object
to 64 bits to ensure that the counter never overflows.
Fix a performance regression caused by a bug fix in patch release
3.41.1.
Fix a few incorrect assert() statements.
Hashes:
SQLITE_SOURCE_ID: 2023-03-22 11:56:21
0d1fc92f94cb6b76bffe3ec34d69cffde2924203304e8ffc4155597af0c191da
SHA3-256 for sqlite3.c:
c83f68b7aac1e7d3ed0fcdb9857742f024449e1300bfb3375131a6180b36cf7c

2023-03-10 (3.41.1)
Provide compile-time options -DHAVE_LOG2=0 and -DHAVE_LOG10=0 to
enable SQLite to be compiled on systems that omit the standard
library functions log2() and log10(), repectively.
Ensure that the datatype for column t1.x in "CREATE TABLE t1 AS
SELECT CAST(7 AS INT) AS x;" continues to be INT and is not NUM,
for historical compatibility.
Enhance PRAGMA integrity_check to detect when extra bytes appear
at the end of an index record.
Fix various obscure bugs reported by the user community. See the
timeline of changes for details.
Hashes:
SQLITE_SOURCE_ID: 2023-03-10 12:13:52
20399f3eda5ec249d147ba9e48da6e87f969d7966a9a896764ca437ff7e737ff
SHA3-256 for sqlite3.c:
d0d9db8425570f4a57def04fb8f4ac84f5c3e4e71d3d4d10472e3639c5fdf09f

2023-02-21 (3.41.0)
Query planner improvements:
Make use of indexed expressions within an aggregate query that
includes a GROUP BY clause.
The query planner has improved awareness of when an index is a
covering index and adjusts predicted runtimes accordingly.
The query planner is more aggressive about using co-routines rather
than materializing subqueries and views.
Queries against the built-in table-valued functions json_tree()
and json_each() will now usually treat "ORDER BY rowid" as a no-op.
Enhance the ability of the query planner to use indexed expressions
even if the expression has been modified by the constant-propagation
optimization. (See forum thread 0a539c7.)
Add the built-in unhex() SQL function.
Add the base64 and base85 application-defined functions as an
extension and include that extension in the CLI.
Add the sqlite3_stmt_scanstatus_v2() interface. (This interface is
only available if SQLite is compiled using SQLITE_ENABLE_STMT_SCANSTATUS.)
In-memory databases created using sqlite3_deserialize() now report
their filename as an empty string, not as 'x'.
Changes to the CLI:
Add the new base64() and base85() SQL functions
Enhanced EXPLAIN QUERY PLAN output using the new
sqlite3_stmt_scanstatus_v2() interface when compiled using
SQLITE_ENABLE_STMT_SCANSTATUS.
The ".scanstats est" command provides query planner estimates in
profiles.
The continuation prompt indicates if the input is currently inside
of a string literal, identifier literal, comment, trigger definition,
etc.
Enhance the --safe command-line option to disallow dangerous SQL
functions.
The double-quoted string misfeature is now disabled by default for
CLI builds. Legacy use cases can reenable the misfeature at run-time
using the ".dbconfig dqs_dml on" and ".dbconfig dqs_ddl on" commands.
Enhance the PRAGMA integrity_check command so that it detects when
text strings in a table are equivalent to but not byte-for-byte
identical to the same strings in the index.
Enhance the carray table-valued function so that it is able to bind
an array of BLOB objects.
Added the sqlite3_is_interrupted() interface.
Long-running calls to sqlite3_prepare() and similar now invoke the
progress handler callback and react to sqlite3_interrupt().
The sqlite3_vtab_in_first() and sqlite3_vtab_in_next() functions
are enhanced so that they reliably detect if they are invoked on
a parameter that was not selected for multi-value IN processing
using sqlite3_vtab_in(). They return SQLITE_ERROR instead of
SQLITE_MISUSE in this case.
The parser now ignores excess parentheses around a subquery on the
right-hand side of an IN operator, so that SQLite now works the
same as PostgreSQL in this regard. Formerly, SQLite treated the
subquery as an expression with an implied "LIMIT 1".
Added the SQLITE_FCNTL_RESET_CACHE option to the sqlite3_file_control()
API.
Makefile improvements:
The new makefile target "sqlite3r.c" builds an amalgamation that
includes the recovery extension.
New makefile targets "devtest" and "releasetest" for running a
quick developmental test prior to doing a check-in and for doing
a full release test, respectively.
Miscellaneous performance enhancements.
Hashes:
SQLITE_SOURCE_ID: 2023-02-21 18:09:37
05941c2a04037fc3ed2ffae11f5d2260706f89431f463518740f72ada350866d
SHA3-256 for sqlite3.c:
02bd9e678460946810801565667fdb8f0c29c78e51240512d2e5bb3dbdee7464

2022-12-28 (3.40.1)
Fix the --safe command-line option to the CLI such that it correctly
disallows the use of SQL functions like writefile() that can cause
harmful side-effects.
Fix a potential infinite loop in the memsys5 alternative memory
allocator. This bug was introduced by a performance optimization
in version 3.39.0.
Various other obscure fixes.
Hashes:
SQLITE_SOURCE_ID: 2022-12-28 14:03:47
df5c253c0b3dd24916e4ec7cf77d3db5294cc9fd45ae7b9c5e82ad8197f38a24
SHA3-256 for sqlite3.c:
4d6800e9032ff349376fe612e422b49ba5eb4e378fac0b3e405235d09dd366ab

2022-11-16 (3.40.0)
Add support for compiling SQLite to WASM and running it in web
browsers. NB: The WASM build and its interfaces are considered
"beta" and are subject to minor changes if the need arises. We
anticipate finalizing the interface for the next release.
Add the recovery extension that might be able to recover some
content from a corrupt database file.
Query planner enhancements:
Recognize covering indexes on tables with more than 63 columns
where columns beyond the 63rd column are used in the query and/or
are referenced by the index.
Extract the values of expressions contained within expression
indexes where practical, rather than recomputing the expression.
The NOT NULL and IS NULL operators (and their equivalents) avoid
loading the content of large strings and BLOB values from disk.
Avoid materializing a view on which a full scan is performed exactly
once. Use and discard the rows of the view as they are computed.
Allow flattening of a subquery that is the right-hand operand of
a LEFT JOIN in an aggregate query.
A new typedef named sqlite3_filename is added and used to represent
the name of a database file. Various interfaces are modified to
use the new typedef instead of "char*". This interface change should
be fully backwards compatible, though it might cause (harmless)
compiler warnings when rebuilding some legacy applications.
Add the sqlite3_value_encoding() interface.
Security enhancement: SQLITE_DBCONFIG_DEFENSIVE is augmented to
prohibit changing the schema_version. The schema_version becomes
read-only in defensive mode.
Enhancements to the PRAGMA integrity_check statement:
Columns in non-STRICT tables with TEXT affinity should not contain
numeric values.
Columns in non-STRICT tables with NUMERIC affinity should not
contain TEXT values that could be converted into numbers.
Verify that the rows of a WITHOUT ROWID table are in the correct
order.
Enhance the VACUUM INTO statement so that it honors the PRAGMA
synchronous setting.
Enhance the sqlite3_strglob() and sqlite3_strlike() APIs so that
they are able to accept NULL pointers for their string parameters
and still generate a sensible result.
Provide the new SQLITE_MAX_ALLOCATION_SIZE compile-time option for
limiting the size of memory allocations.
Change the algorithm used by SQLite's built-in pseudo-random number
generator (PRNG) from RC4 to Chacha20.
Allow two or more indexes to have the same name as long as they
are all in separate schemas.
Miscellaneous performance optimizations result in about 1% fewer
CPU cycles used on typical workloads.
Hashes:
SQLITE_SOURCE_ID: 2022-11-16 12:10:08
89c459e766ea7e9165d0beeb124708b955a4950d0f4792f457465d71b158d318
SHA3-256 for sqlite3.c:
ab8da6bc754642989e67d581f26683dc705b068cea671970f0a7d32cfacbad19

2022-09-29 (3.39.4)
Fix the build on Windows so that it works with -DSQLITE_OMIT_AUTOINIT
Fix a long-standing problem in the btree balancer that might, in
rare cases, cause database corruption if the application uses an
application-defined page cache.
Enhance SQLITE_DBCONFIG_DEFENSIVE so that it disallows CREATE
TRIGGER statements if one or more of the statements in the body of
the trigger write into shadow tables.
Fix a possible integer overflow in the size computation for a memory
allocation in FTS3.
Fix a misuse of the sqlite3_set_auxdata() interface in the ICU
Extension.
Hashes:
SQLITE_SOURCE_ID: 2022-09-29 15:55:41
a29f9949895322123f7c38fbe94c649a9d6e6c9cd0c3b41c96d694552f26b309
SHA3-256 for sqlite3.c:
f65082298127e2ddae6539beb94f5204b591df64ba2c7da83c7d0faffd6959d8

2022-09-05 (3.39.3)
Use a statement journal on DML statement affecting two or more
database rows if the statement makes use of a SQL functions that
might abort. See forum thread 9b9e4716c0d7bbd1.
Use a mutex to protect the PRAGMA temp_store_directory and PRAGMA
data_store_directory statements, even though they are deprecated
and documented as not being threadsafe. See forum post 719a11e1314d1c70.
Other bug and warning fixes. See the timeline for details.
Hashes:
SQLITE_SOURCE_ID: 2022-09-05 11:02:23
4635f4a69c8c2a8df242b384a992aea71224e39a2ccab42d8c0b0602f1e826e8
SHA3-256 for sqlite3.c:
2fc273cf8032b601c9e06207efa0ae80eb73d5a1d283eb91096c815fa9640257

2022-07-21 (3.39.2)
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.
Hashes:
SQLITE_SOURCE_ID: 2022-07-21 15:24:47
698edb77537b67c41adc68f9b892db56bcf9a55e00371a61420f3ddd668e6603
SHA3-256 for sqlite3.c:
bffbaafa94706f0ed234f183af3eb46e6485e7e2c75983173ded76e0da805f11

2022-07-13 (3.39.1)
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.
Hashes:
SQLITE_SOURCE_ID: 2022-07-13 19:41:41
7c16541a0efb3985578181171c9f2bb3fdc4bad6a2ec85c6e31ab96f3eff201f
SHA3-256 for sqlite3.c:
6d13fcf1c31133da541d1eb8a83552d746f39b81a0657bd4077fed0221749511

2022-06-25 (3.39.0)
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. If the SQLITE_OPEN_NOFOLLOW flag is used with
sqlite3_open_v2() or similar, the open will fail if any element of
the path is a symbolic link.
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%.
Hashes:
SQLITE_SOURCE_ID: 2022-06-25 14:57:57
14e166f40dbfa6e055543f8301525f2ca2e96a02a57269818b9e69e162e98918
SHA3-256 for sqlite3.c:
d9c439cacad5e4992d0d25989cfd27a4c4f59a3183c97873bc03f0ad1aa78b7a

2022-05-06 (3.38.5)
Fix a blunder in the CLI of the 3.38.4 release.
Hashes:
SQLITE_SOURCE_ID: 2022-05-06 15:25:27
78d9c993d404cdfaa7fdd2973fa1052e3da9f66215cff9c5540ebe55c407d9fe
SHA3-256 for sqlite3.c:
b05ef42ed234009b4b3dfb36c5f5ccf6d728da80f25ee560291269cf6cfe635f

2022-05-04 (3.38.4)
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. Forum thread 2482b32700384a0f.
Other minor patches. See the timeline for details.
Hashes:
SQLITE_SOURCE_ID: 2022-05-04 15:45:55
d402f49871152670a62f4f28cacb15d814f2c1644e9347ad7d258e562978e45e
SHA3-256 for sqlite3.c:
e6a50effb021858c200e885664611ed3c5e949413ff2dca452ac7ee336b9de1d

2022-04-27 (3.38.3)
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.
Hashes:
SQLITE_SOURCE_ID: 2022-04-27 12:03:15
9547e2c38a1c6f751a77d4d796894dec4dc5d8f5d79b1cd39e1ffc50df7b3be4
SHA3-256 for sqlite3.c:
d4d66feffad66ea82073fbb97ae9c84e3615887ebc5168226ccee28d82424517

2022-03-26 (3.38.2)
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.
Hashes:
SQLITE_SOURCE_ID: 2022-03-26 13:51:10
d33c709cc0af66bc5b6dc6216eba9f1f0b40960b9ae83694c986fbf4c1d6f08f
SHA3-256 for sqlite3.c:
0fbac6b6999f894184899431fb77b9792324c61246b2a010d736694ccaa6d613

2022-03-12 (3.38.1)
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.
Hashes:
SQLITE_SOURCE_ID: 2022-03-12 13:37:29
38c210fdd258658321c85ec9c01a072fda3ada94540e3239d29b34dc547a8cbc
SHA3-256 for sqlite3.c:
262ba071e960a8a0a6ce39307ae30244a2b0dc9fe1c4c09d0e1070d4353cd92c

2022-02-22 (3.38.0)
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.
Hashes:
SQLITE_SOURCE_ID: 2022-02-22 18:58:40
40fa792d359f84c3b9e9d6623743e1a59826274e221df1bde8f47086968a1bab
SHA3-256 for sqlite3.c:
a69af0a88d59271a2dd3c846a3e93cbd29e7c499864f6c0462a3b4160bee1762

2022-01-06 (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.
Hashes:
SQLITE_SOURCE_ID: 2022-01-06 13:25:41
872ba256cbf61d9290b571c0e6d82a20c224ca3ad82971edc46b29818d5d17a0
SHA3-256 for sqlite3.c:
1bb01c382295cba85ec4685cedc52a7477cdae71cc37f1ad0f48719a17af1e1e

2021-12-30 (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.
Hashes:
SQLITE_SOURCE_ID: 2021-12-30 15:30:28
378629bf2ea546f73eee84063c5358439a12f7300e433f18c9e1bddd948dea62
SHA3-256 for sqlite3.c:
915afb3f29c2d217ea0c283326a9df7d505e6c73b40236f0b33ded91f812d174

2021-11-27 (3.37.0)
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.
Hashes:
SQLITE_SOURCE_ID: 2021-11-27 14:13:22
bd41822c7424d393a30e92ff6cb254d25c26769889c1499a18a0b9339f5d6c8a
SHA3-256 for sqlite3.c:
a202a950ab401cda052e81259e96d6e64ad91faaaaf5690d769f64c2ab962f27

2021-06-18 (3.36.0)
Improvement to the EXPLAIN QUERY PLAN output to make it easier to
understand.
Byte-order marks at the start of a token are skipped as if they
were whitespace.
An error is raised on any attempt to access the rowid of a VIEW or
subquery. Formerly, the rowid of a VIEW would be indeterminate and
often would be NULL. The -DSQLITE_ALLOW_ROWID_IN_VIEW compile-time
option is available to restore the legacy behavior for applications
that need it.
The sqlite3_deserialize() and sqlite3_serialize() interfaces are
now enabled by default. The -DSQLITE_ENABLE_DESERIALIZE compile-time
option is no longer required. Instead, there is a new
-DSQLITE_OMIT_DESERIALIZE compile-time option to omit those
interfaces.
The "memdb" VFS now allows the same in-memory database to be shared
among multiple database connections in the same process as long as
the database name begins with "/".
Back out the EXISTS-to-IN optimization (item 8b in the SQLite 3.35.0
change log) as it was found to slow down queries more often than
speed them up.
Improve the constant-propagation optimization so that it works on
non-join queries.
The REGEXP extension is now included in CLI builds.
Hashes:
SQLITE_SOURCE_ID: 2021-06-18 18:36:39
5c9a6c06871cb9fe42814af9c039eb6da5427a6ec28f187af7ebfb62eafa66e5
SHA3-256 for sqlite3.c:
2a8e87aaa414ac2d45ace8eb74e710935423607a8de0fafcb36bbde5b952d157

2021-04-19 (3.35.5)
Fix defects in the new ALTER TABLE DROP COLUMN feature that could
corrupt the database file.
Fix an obscure query optimizer problem that might cause an incorrect
query result.
Hashes:
SQLITE_SOURCE_ID: 2021-04-19 18:32:05
1b256d97b553a9611efca188a3d995a2fff712759044ba480f9a0c9e98fae886
SHA3-256 for sqlite3.c:
e42291343e8f03940e57fffcf1631e7921013b94419c2f943e816d3edf4e1bbe

2021-04-02 (3.35.4)
Fix a defect in the query planner optimization identified by item
8b above. Ticket de7db14784a08053.
Fix a defect in the new RETURNING syntax. Ticket 132994c8b1063bfb.
Fix the new RETURNING feature so that it raises an error if one of
the terms in the RETURNING clause references a unknown table,
instead of silently ignoring that error.
Fix an assertion associated with aggregate function processing that
was incorrectly triggered by the push-down optimization.
Hashes:
SQLITE_SOURCE_ID: 2021-04-02 15:20:15
5d4c65779dab868b285519b19e4cf9d451d50c6048f06f653aa701ec212df45e
SHA3-256 for sqlite3.c:
528b8a26bf5ffd4c7b4647b5b799f86e8fb1a075f715b87a414e94fba3d09dbe

2021-03-26 (3.35.3)
Enhance the OP_OpenDup opcode of the bytecode engine so that it
works even if the cursor being duplicated itself came from OP_OpenDup.
Fix for ticket bb8a9fd4a9b7fce5. This problem only came to light
due to the recent MATERIALIZED hint enhancement.
When materializing correlated common table expressions, do so
separately for each use case, as that is required for correctness.
This fixes a problem that was introduced by the MATERIALIZED hint
enhancement.
Fix a problem in the filename normalizer of the unix VFS.
Fix the "box" output mode in the CLI so that it works with statements
that returns one or more rows of zero columns (such as PRAGMA
incremental_vacuum). Forum post afbbcb5b72.
Improvements to error messages generated by faulty common table
expressions. Forum post aa5a0431c99e.
Fix some incorrect assert() statements.
Fix to the SELECT statement syntax diagram so that the FROM clause
syntax is shown correctly. Forum post 9ed02582fe.
Fix the EBCDIC character classifier so that it understands newlines
as whitespace. Forum post 58540ce22dcd.
Improvements the xBestIndex method in the implementation of the
(unsupported) wholenumber virtual table extension so that it does
a better job of convincing the query planner to avoid trying to
materialize a table with an infinite number of rows. Forum post
b52a020ce4.
Hashes:
SQLITE_SOURCE_ID: 2021-03-26 12:12:52
4c5e6c200adc8afe0814936c67a971efc516d1bd739cb620235592f18f40be2a
SHA3-256 for sqlite3.c:
91ca6c0a30ebfdba4420bb35f4fd9149d13e45fc853d86ad7527db363e282683

2021-03-17 (3.35.2)
Fix a problem in the appendvfs.c extension that was introduced into
version 3.35.0.
Ensure that date/time functions with no arguments (which generate
responses that depend on the current time) are treated as
non-deterministic functions. Ticket 2c6c8689fb5f3d2f
Fix a problem in the sqldiff utility program having to do with
unusual whitespace characters in a virtual table definition.
Limit the new UNION ALL optimization described by item 8c in the
3.35.0 release so that it does not try to make too many new
subqueries. See forum thread 140a67d3d2 for details.
Hashes:
SQLITE_SOURCE_ID: 2021-03-17 19:07:21
ea80f3002f4120f5dcee76e8779dfdc88e1e096c5cdd06904c20fd26d50c3827
SHA3-256 for sqlite3.c:
e8edc7b1512a2e050d548d0840bec6eef83cc297af1426c34c0ee8720f378a11

2021-03-15 (3.35.1)
Fix a bug in the new DROP COLUMN feature when used on columns that
are indexed and that are quoted in the index definition.
Improve the built-in documentation for the .dump command in the
CLI.
Hashes:
SQLITE_SOURCE_ID: 2021-03-15 16:53:57
aea12399bf1fdc76af43499d4624c3afa17c3e6c2459b71c195804bb98def66a
SHA3-256 for sqlite3.c:
fc79e27fd030226c07691b7d7c23aa81c8d46bc3bef5af39060e1507c82b0523

2021-03-12 (3.35.0)
Added built-in SQL math functions(). (Requires the
-DSQLITE_ENABLE_MATH_FUNCTIONS compile-time option.)
Added support for ALTER TABLE DROP COLUMN.
Generalize UPSERT:
Allow multiple ON CONFLICT clauses that are evaluated in order,
The final ON CONFLICT clause may omit the conflict target and yet
still use DO UPDATE.
Add support for the RETURNING clause on DELETE, INSERT, and UPDATE
statements.
Use less memory when running VACUUM on databases containing very
large TEXT or BLOB values. It is no longer necessary to hold the
entire TEXT or BLOB in memory all at once.
Add support for the MATERIALIZED and NOT MATERIALIZED hints when
specifying common table expressions. The default behavior was
formerly NOT MATERIALIZED, but is now changed to MATERIALIZED for
CTEs that are used more than once.
The SQLITE_DBCONFIG_ENABLE_TRIGGER and SQLITE_DBCONFIG_ENABLE_VIEW
settings are modified so that they only control triggers and views
in the main database schema or in attached database schemas and
not in the TEMP schema. TEMP triggers and views are always allowed.
Query planner/optimizer improvements:
Enhancements to the min/max optimization so that it works better
with the IN operator and the OP_SeekScan optimization of the previous
release.
Attempt to process EXISTS operators in the WHERE clause as if they
were IN operators, in cases where this is a valid transformation
and seems likely to improve performance.
Allow UNION ALL sub-queries to be flattened even if the parent
query is a join.
Use an index, if appropriate, on IS NOT NULL expressions in the
WHERE clause, even if STAT4 is disabled.
Expressions of the form "x IS NULL" or "x IS NOT NULL" might be
converted to simply FALSE or TRUE, if "x" is a column that has a
"NOT NULL" constraint and is not involved in an outer join.
Avoid checking foreign key constraints on an UPDATE statement if
the UPDATE does not modify any columns associated with the foreign
key.
Allow WHERE terms to be pushed down into sub-queries that contain
window functions, as long as the WHERE term is made up of entirely
of constants and copies of expressions found in the PARTITION BY
clauses of all window functions in the sub-query.
CLI enhancements:
Enhance the ".stats" command to accept new arguments "stmt" and
"vmstep", causing prepare statement statistics and only the
virtual-machine step count to be shown, respectively.
Add the ".filectrl data_version" command.
Enhance the ".once" and ".output" commands so that if the destination
argument begins with "|" (indicating that output is redirected into
a pipe) then the argument does not need to be quoted.
Bug fixes:
Fix a potential NULL pointer dereference when processing a
syntactically incorrect SELECT statement with a correlated WHERE
clause and a "HAVING 0" clause. (Also fixed in the 3.34.1 patch
release.)
Fix a bug in the IN-operator optimization of version 3.33.0 that
can cause an incorrect answer.
Fix incorrect answers from the LIKE operator if the pattern ends
with "%" and there is an "ESCAPE '_'" clause.
Hashes:
SQLITE_SOURCE_ID: 2021-03-12 15:10:09
acd63062eb06748bfe9e4886639e4f2b54ea6a496a83f10716abbaba4115500b
SHA3-256 for sqlite3.c:
73a740d881735bef9de7f7bce8c9e6b9e57fe3e77fa7d76a6e8fc5c262fbaedf

2021-01-20 (3.34.1)
Fix a potential use-after-free bug when processing a a subquery
with both a correlated WHERE clause and a "HAVING 0" clause and
where the parent query is an aggregate.
Fix documentation typos
Fix minor problems in extensions.
Hashes:
SQLITE_SOURCE_ID: 2021-01-20 14:10:07
10e20c0b43500cfb9bbc0eaa061c57514f715d87238f4d835880cd846b9ebd1f
SHA3-256 for sqlite3.c:
799a7be90651fc7296113b641a70b028c142d767b25af1d0a78f93dcf1a2bf20

2020-12-01 (3.34.0)
Added the sqlite3_txn_state() interface for reporting on the current
transaction state of the database connection.
Enhance recursive common table expressions to support two or more
recursive terms as is done by SQL Server, since this helps make
queries against graphs easier to write and faster to execute.
Improved error messages on CHECK constraint failures.
CLI enhancements:
The .read dot-command now accepts a pipeline in addition to a
filename.
Added options --data-only and --nosys to the .dump dot-command.
Added the --nosys option to the .schema dot-command.
Table name quoting works correctly for the .import dot-command.
The generate_series(START,END,STEP) table-valued function extension
is now built into the CLI.
The .databases dot-command now shows the status of each database
file as determined by sqlite3_db_readonly() and sqlite3_txn_state().
Added the --tabs command-line option that sets .mode tabs.
The --init option reports an error if the file named as its argument
cannot be opened. The --init option also now honors the --bail
option.
Query planner improvements:
Improved estimates for the cost of running a DISTINCT operator.
When doing an UPDATE or DELETE using a multi-column index where
only a few of the earlier columns of the index are useful for the
index lookup, postpone doing the main table seek until after all
WHERE clause constraints have been evaluated, in case those
constraints can be covered by unused later terms of the index, thus
avoiding unnecessary main table seeks.
The new OP_SeekScan opcode is used to improve performance of
multi-column index look-ups when later columns are constrained by
an IN operator.
The BEGIN IMMEDIATE and BEGIN EXCLUSIVE commands now work even if
one or more attached database files are read-only.
Enhanced FTS5 to support trigram indexes.
Improved performance of WAL mode locking primitives in cases where
there are hundreds of connections all accessing the same database
file at once.
Enhanced the carray() table-valued function to include a single-argument
form that is bound using the auxiliary sqlite3_carray_bind()
interface.
The substr() SQL function can now also be called "substring()" for
compatibility with SQL Server.
The syntax diagrams are now implemented as Pikchr scripts and
rendered as SVG for improved legibility and ease of maintenance.
Hashes:
SQLITE_SOURCE_ID: 2020-12-01 16:14:00
a26b6597e3ae272231b96f9982c3bcc17ddec2f2b6eb4df06a224b91089fed5b
SHA3-256 for sqlite3.c:
fbd895b0655a337b2cd657675f314188a4e9fe614444cc63dfeb3f066f674514

2020-08-14 (3.33.0)
Support for UPDATE FROM following the PostgreSQL syntax.
Increase the maximum size of database files to 281 TB.
Extended the PRAGMA integrity_check statement so that it can
optionally be limited to verifying just a single table and its
indexes, rather than the entire database file.
Added the decimal extension for doing arbitrary-precision decimal
arithmetic.
Enhancements to the ieee754 extension for working with IEEE 754
binary64 numbers.
CLI enhancements:
Added four new output modes: "box", "json", "markdown", and "table".
The "column" output mode automatically expands columns to contain
the longest output row and automatically turns ".header" on if it
has not been previously set.
The "quote" output mode honors ".separator"
The decimal extension and the ieee754 extension are built-in to
the CLI
Query planner improvements:
Add the ability to find a full-index-scan query plan for queries
using INDEXED BY which previously would fail with "no query solution".
Do a better job of detecting missing, incomplete, and/or dodgy
sqlite_stat1 data and generates good query plans in spite of the
misinformation.
Improved performance of queries like "SELECT min(x) FROM t WHERE
y IN (?,?,?)" assuming an index on t(x,y).
In WAL mode, if a writer crashes and leaves the shm file in an
inconsistent state, subsequent transactions are now able to recover
the shm file even if there are active read transactions. Before
this enhancement, shm file recovery that scenario would result in
an SQLITE_PROTOCOL error.
Hashes:
SQLITE_SOURCE_ID: 2020-08-14 13:23:32
fca8dc8b578f215a969cd899336378966156154710873e68b3d9ac5881b0ff3f
SHA3-256 for sqlite3.c:
d00b7fffa6d33af2303430eaf394321da2960604d25a4471c7af566344f2abf9

2020-06-18 (3.32.3)
Various minor bug fixes including fixes for tickets 8f157e8010b22af0,
9fb26d37cefaba40, e367f31901ea8700, b706351ce2ecf59a, 7c6d876f84e6e7e2,
and c8d3b9f0a750a529.
Hashes:
SQLITE_SOURCE_ID: 2020-06-18 14:00:33
7ebdfa80be8e8e73324b8d66b3460222eb74c7e9dfd655b48d6ca7e1933cc8fd
SHA3-256 for sqlite3.c:
b62b77ee1c561a69a71bb557694aaa5141f1714c1ff6cc1ba8aa8733c92d4f52

2020-06-04 (3.32.2)
Fix a long-standing bug in the byte-code engine that can cause a
COMMIT command report as success when in fact it failed to commit.
Ticket 810dc8038872e212
Hashes:
SQLITE_SOURCE_ID: 2020-06-04 12:58:43
ec02243ea6ce33b090870ae55ab8aa2534b54d216d45c4aa2fdbb00e86861e8c
SHA3-256 for sqlite3.c:
f17a2a57f7eebc72d405f3b640b4a49bcd02364a9c36e04feeb145eccafa3f8d

2020-05-25 (3.32.1)
Fix two long-standing bugs that allow malicious SQL statements to
crash the process that is running SQLite. These bugs were announced
by a third-party approximately 24 hours after the 3.32.0 release
but are not specific to the 3.32.0 release.
Other minor compiler-warning fixes and whatnot.
Hashes:
SQLITE_SOURCE_ID: 2020-05-25 16:19:56
0c1fcf4711a2e66c813aed38cf41cd3e2123ee8eb6db98118086764c4ba83350
SHA3-256 for sqlite3.c:
f695ae21abf045e4ee77980a67ab2c6e03275009e593ee860a2eabf840482372

2020-05-22 (3.32.0)
Added support for approximate ANALYZE using the PRAGMA analysis_limit
command.
Added the bytecode virtual table.
Add the checksum VFS shim to the set of run-time loadable extensions
included in the source tree.
Added the iif() SQL function.
INSERT and UPDATE statements now always apply column affinity before
computing CHECK constraints. This bug fix could, in theory, cause
problems for legacy databases with unorthodox CHECK constraints
the require the input type for an INSERT is different from the
declared column type. See ticket 86ba67afafded936 for more information.
Added the sqlite3_create_filename(), sqlite3_free_filename(), and
sqlite3_database_file_object() interfaces to better support of VFS
shim implementations.
Increase the default upper bound on the number of parameters from
999 to 32766.
Added code for the UINT collating sequence as an optional loadable
extension.
Enhancements to the CLI:
Add options to the .import command: --csv, --ascii, --skip
The .dump command now accepts multiple LIKE-pattern arguments and
outputs the union of all matching tables.
Add the .oom command in debugging builds
Add the --bom option to the .excel, .output, and .once commands.
Enhance the .filectrl command to support the --schema option.
The UINT collating sequence extension is automatically loaded
The ESCAPE clause of a LIKE operator now overrides wildcard
characters, so that the behavior matches what PostgreSQL does.
SQLITE_SOURCE_ID: 2020-05-22 17:46:16
5998789c9c744bce92e4cff7636bba800a75574243d6977e1fc8281e360f8d5a
SHA3-256 for sqlite3.c:
33ed868b21b62ce1d0352ed88bdbd9880a42f29046497a222df6459fc32a356f

2020-01-27 (3.31.1)
Revert the data layout for an internal-use-only SQLite data structure.
Applications that use SQLite should never reference internal SQLite
data structures, but some do anyhow, and a change to one such data
structure in 3.30.0 broke a popular and widely-deployed application.
Reverting that change in SQLite, at least temporarily, gives
developers of misbehaving applications time to fix their code.
Fix a typos in the sqlite3ext.h header file that prevented the
sqlite3_stmt_isexplain() and sqlite3_value_frombind() interfaces
from being called from run-time loadable extensions.
Hashes:
SQLITE_SOURCE_ID: 2020-01-27 19:55:54
3bfa9cc97da10598521b342961df8f5f68c7388fa117345eeb516eaa837bb4d6
SHA3-256 for sqlite3.c:
de465c64f09529429a38cbdf637acce4dfda6897f93e3db3594009e0fed56d27

2020-01-22 (3.31.0)
Add support for generated columns.
Add the sqlite3_hard_heap_limit64() interface and the corresponding
PRAGMA hard_heap_limit command.
Enhance the function_list pragma to show the number of arguments
on each function, the type of function (scalar, aggregate, window),
and the function property flags SQLITE_DETERMINISTIC, SQLITE_DIRECTONLY,
SQLITE_INNOCUOUS, and/or SQLITE_SUBTYPE.
Add the aggregated mode feature to the DBSTAT virtual table.
Add the SQLITE_OPEN_NOFOLLOW option to sqlite3_open_v2() that
prevents SQLite from opening symbolic links.
Added the "#-N" array notation for JSON function path arguments.
Added the SQLITE_DBCONFIG_TRUSTED_SCHEMA connection setting which
is also controllable via the new trusted_schema pragma and at
compile-time using the -DSQLITE_TRUSTED_SCHEMA compile-time option.
Added APIs sqlite3_filename_database(), sqlite3_filename_journal(),
and sqlite3_filename_wal() which are useful for specialized
extensions.
Add the sqlite3_uri_key() interface.
Upgraded the sqlite3_uri_parameter() function so that it works with
the rollback journal or WAL filename in addition to the database
filename.
Provide the ability to tag application-defined SQL functions with
new properties SQLITE_INNOCUOUS or SQLITE_DIRECTONLY.
Add new verbs to sqlite3_vtab_config() so that the xConnect method
of virtual tables can declare the virtual table as SQLITE_VTAB_INNOCUOUS
or SQLITE_VTAB_DIRECTONLY.
Faster response to sqlite3_interrupt().
Added the uuid.c extension module implementing functions for
processing RFC-4122 UUIDs.
The lookaside memory allocator is enhanced to support two separate
memory pools with different sized allocations in each pool. This
allows more memory allocations to be covered by lookaside while at
the same time reducing the heap memory usage to 48KB per connection,
down from 120KB.
The legacy_file_format pragma is deactivated. It is now a no-op.
In its place, the SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option to
sqlite3_db_config() is provided. The legacy_file_format pragma is
deactivated because (1) it is rarely useful and (2) it is incompatible
with VACUUM in schemas that have tables with both generated columns
and descending indexes. Ticket 6484e6ce678fffab
Hashes:
SQLITE_SOURCE_ID: 2020-01-22 18:38:59
f6affdd41608946fcfcea914ece149038a8b25a62bbe719ed2561c649b86d824
SHA3-256 for sqlite3.c:
a5fca0b9f8cbf80ac89b97193378c719d4af4b7d647729d8df9c0c0fca7b1388

2019-10-10 (3.30.1)
Fix a bug in the query flattener that might cause a segfault for
nested queries that use the new FILTER clause on aggregate functions.
Ticket 1079ad19993d13fa
Cherrypick fixes for other obscure problems found since the 3.30.0
release
Hashes:
SQLITE_SOURCE_ID: 2019-10-10 20:19:45
18db032d058f1436ce3dea84081f4ee5a0f2259ad97301d43c426bc7f3df1b0b
SHA3-256 for sqlite3.c:
f96fafe4c110ed7d77fc70a7d690e5edd1e64fefb84b3b5969a722d885de1f2d

2019-10-04 (3.30.0)
Add support for the FILTER clause on aggregate functions.
Add support for the NULLS FIRST and NULLS LAST syntax in ORDER BY
clauses.
The index_info and index_xinfo pragmas are enhanced to provide
information about the on-disk representation of WITHOUT ROWID
tables.
Add the sqlite3_drop_modules() interface, allowing applications to
disable automatically loaded virtual tables that they do not need.
Improvements to the .recover dot-command in the CLI so that it
recovers more content from corrupt database files.
Enhance the RBU extension to support indexes on expressions.
Change the schema parser so that it will error out if any of the
type, name, and tbl_name columns of the sqlite_master table have
been corrupted and the database connection is not in writable_schema
mode.
The PRAGMA function_list, PRAGMA module_list, and PRAGMA pragma_list
commands are now enabled in all builds by default. Disable them
using -DSQLITE_OMIT_INTROSPECTION_PRAGMAS.
Add the SQLITE_DBCONFIG_ENABLE_VIEW option for sqlite3_db_config().
Added the TCL Interface config method in order to be able to disable
SQLITE_DBCONFIG_ENABLE_VIEW as well as control other sqlite3_db_config()
options from TCL.
Added the SQLITE_DIRECTONLY flag for application-defined SQL
functions to prevent those functions from being used inside triggers
and views.
The legacy SQLITE_ENABLE_STAT3 compile-time option is now a no-op.
Hashes:
SQLITE_SOURCE_ID: 2019-10-04 15:03:17
c20a35336432025445f9f7e289d0cc3e4003fb17f45a4ce74c6269c407c6e09f
SHA3-256 for sqlite3.c:
f04393dd47205a4ee2b98ff737dc51a3fdbcc14c055b88d58f5b27d0672158f5

2019-07-10 (3.29.0)
Added the SQLITE_DBCONFIG_DQS_DML and SQLITE_DBCONFIG_DQS_DDL
actions to sqlite3_db_config() for activating and deactivating the
double-quoted string literal misfeature. Both default to "on" for
legacy compatibility, but developers are encouraged to turn them
"off", perhaps using the -DSQLITE_DQS=0 compile-time option.
-DSQLITE_DQS=0 is now a recommended compile-time option.
Improvements to the query planner:
Improved optimization of AND and OR operators when one or the other
operand is a constant.
Enhancements to the LIKE optimization for cases when the left-hand
side column has numeric affinity.
Added the "sqlite_dbdata" virtual table for extracting raw low-level
content from an SQLite database, even a database that is corrupt.
Improvements to rounding behavior, so that the results of rounding
binary numbers using the round() function are closer to what people
who are used to thinking in decimal actually expect.
Enhancements to the CLI:
Add the ".recover" command which tries to recover as much content
as possible from a corrupt database file.
Add the ".filectrl" command useful for testing.
Add the long-standing ".testctrl" command to the ".help" menu.
Added the ".dbconfig" command
Hashes:
SQLITE_SOURCE_ID: 2019-07-10 17:32:03
fc82b73eaac8b36950e527f12c4b5dc1e147e6f4ad2217ae43ad82882a88bfa6
SHA3-256 for sqlite3.c:
d9a5daf7697a827f4b2638276ce639fa04e8e8bb5fd3a6b683cfad10f1c81b12

2019-04-16 (3.28.0)
Enhanced window functions:
Add support the EXCLUDE clause.
Add support for window chaining.
Add support for GROUPS frames.
Add support for "<expr> PRECEDING" and "<expr> FOLLOWING" boundaries
in RANGE frames.
Added the new sqlite3_stmt_isexplain(S) interface for determining
whether or not a prepared statement is an EXPLAIN.
Enhanced VACUUM INTO so that it works for read-only databases.
New query optimizations:
Enable the LIKE optimization for cases when the ESCAPE keyword is
present and PRAGMA case_sensitive_like is on.
In queries that are driven by a partial index, avoid unnecessary
tests of the constraint named in the WHERE clause of the partial
index, since we know that constraint must always be true.
Enhancements to the TCL Interface:
Added the -returntype option to the function method.
Added the new bind_fallback method.
Enhancements to the CLI:
Added support for bound parameters and the .parameter command.
Fix the readfile() function so that it returns an empty BLOB rather
than throwing an out-of-memory error when reading an empty file.
Fix the writefile() function so that when it creates new directories
along the path of a new file, it gives them umask permissions rather
than the same permissions as the file.
Change --update option in the .archive command so that it skips
files that are already in the archive and are unchanged. Add the
new --insert option that works like --update used to work.
Added the fossildelta.c extension that can create, apply, and
deconstruct the Fossil DVCS file delta format that is used by the
RBU extension.
Added the SQLITE_DBCONFIG_WRITABLE_SCHEMA verb for the sqlite3_db_config()
interface, that does the same work as PRAGMA writable_schema without
using the SQL parser.
Added the sqlite3_value_frombind() API for determining if the
argument to an SQL function is from a bound parameter.
Security and compatibilities enhancements to fts3_tokenizer():
The fts3_tokenizer() function always returns NULL unless either
the legacy application-defined FTS3 tokenizers interface are enabled
using the sqlite3_db_config(SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER)
setting, or unless the first argument to fts3_tokenizer() is a
bound parameter.
The two-argument version of fts3_tokenizer() accepts a pointer to
the tokenizer method object even without the
sqlite3_db_config(SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER) setting
if the second argument is a bound parameter
Improved robustness against corrupt database files.
Miscellaneous performance enhancements
Established a Git mirror of the offical SQLite source tree. The
canonical sources for SQLite are maintained using the Fossil DVCS
at https://sqlite.org/src. The Git mirror can be seen at
https://github.com/sqlite/sqlite.
Hashes:
SQLITE_SOURCE_ID: 2019-04-16 19:49:53
884b4b7e502b4e991677b53971277adfaf0a04a284f8e483e2553d0f83156b50
SHA3-256 for sqlite3.c:
411efca996b65448d9798eb203d6ebe9627b7161a646f5d00911e2902a57b2e9

2019-02-25 (3.27.2)
Fix a bug in the IN operator that was introduced by an attempted
optimization in version 3.27.0. Ticket df46dfb631f75694
Fix a bug causing a crash when a window function is misused. Ticket
4feb3159c6bc3f7e33959.
Fix various documentation typos
Hashes:
SQLITE_SOURCE_ID:
bd49a8271d650fa89e446b42e513b595a717b9212c91dd384aab871fc1d0f6d7
SHA3-256 for sqlite3.c:
1dbae33bff261f979d0042338f72c9e734b11a80720fb32498bae9150cc576e7

2019-02-08 (3.27.1)
Fix a bug in the query optimizer: an adverse interaction between
the OR optimization and the optimization that tries to use values
read directly from an expression index instead of recomputing the
expression. Ticket 4e8e4857d32d401f
Hashes:
SQLITE_SOURCE_ID: 2019-02-08 13:17:39
0eca3dd3d38b31c92b49ca2d311128b74584714d9e7de895b1a6286ef959a1dd
SHA3-256 for sqlite3.c:
11c14992660d5ac713ea8bea48dc5e6123f26bc8d3075fe5585d1a217d090233

2019-02-07 (3.27.0)
Added the VACUUM INTO command
Issue an SQLITE_WARNING message on the error log if a double-quoted
string literal is used.
The sqlite3_normalized_sql() interface works on any prepared
statement created using sqlite3_prepare_v2() or sqlite3_prepare_v3().
It is no longer necessary to use sqlite3_prepare_v3() with
SQLITE_PREPARE_NORMALIZE in order to use sqlite3_normalized_sql().
Added the remove_diacritics=2 option to FTS3 and FTS5.
Added the SQLITE_PREPARE_NO_VTAB option to sqlite3_prepare_v3().
Use that option to prevent circular references to shadow tables
from causing resource leaks.
Enhancements to the sqlite3_deserialize() interface:
Add the SQLITE_FCNTL_SIZE_LIMIT file-control for setting an upper
bound on the size of the in-memory database created by sqlite3_deserialize.
The default upper bound is 1GiB, or whatever alternative value is
specified by sqlite3_config(SQLITE_CONFIG_MEMDB_MAXSIZE) and/or
SQLITE_MEMDB_DEFAULT_MAXSIZE.
Honor the SQLITE_DESERIALIZE_READONLY flag, which was previously
described in the documentation, but was previously a no-op.
Enhance the "deserialize" command of the TCL Interface to give it
new "--maxsize N" and "--readonly BOOLEAN" options.
Enhancements to the CLI, mostly to support testing and debugging
of the SQLite library itself:
Add support for ".open --hexdb". The "dbtotxt" utility program used
to generate the text for the "hexdb" is added to the source tree.
Add support for the "--maxsize N" option on ".open --deserialize".
Add the "--memtrace" command-line option, to show all memory
allocations and deallocations.
Add the ".eqp trace" option on builds with SQLITE_DEBUG, to enable
bytecode program listing with indentation and PRAGMA vdbe_trace
all in one step.
Add the ".progress" command for accessing the sqlite3_progress_handler()
interface.
Add the "--async" option to the ".backup" command.
Add options "--expanded", "--normalized", "--plain", "--profile",
"--row", "--stmt", and "--close" to the ".trace" command.
Increased robustness against malicious SQL that is run against a
maliciously corrupted database.
Bug fixes:
Do not use a partial index to do a table scan on an IN operator.
Ticket 1d958d90596593a774.
Fix the query flattener so that it works on queries that contain
subqueries that use window functions. Ticket 709fcd17810f65f717
Ensure that ALTER TABLE modifies table and column names embedded
in WITH clauses that are part of views and triggers.
Fix a parser bug that prevented the use of parentheses around
table-valued functions.
Fix a problem with the OR optimization on indexes on expressions.
Ticket d96eba87698a428c1d.
Fix a problem with the LEFT JOIN strength reduction optimization
in which the optimization was being applied inappropriately due to
an IS NOT NULL operator. Ticket 5948e09b8c415bc45d.
Fix the REPLACE command so that it is no longer able to sneak a
NULL value into a NOT NULL column even if the NOT NULL column has
a default value of NULL. Ticket e6f1f2e34dceeb1ed6
Fix a problem with the use of window functions used within correlated
subqueries. Ticket d0866b26f83e9c55e3
Fix the ALTER TABLE RENAME COLUMN command so that it works for
tables that have redundant UNIQUE constraints. Ticket bc8d94f0fbd633fd9a
Fix a bug that caused zeroblob values to be truncated when inserted
into a table that uses an expression index. Ticket bb4bdb9f7f654b0bb9
Hashes:
SQLITE_SOURCE_ID: "2019-02-07 17:02:52
97744701c3bd414e6c9d7182639d8c2ce7cf124c4fce625071ae65658ac61713
"
SHA3-256 for sqlite3.c:
ca011a10ee8515b33e5643444b98ee3d74dc45d3ac766c3700320def52bc6aba

Initial revision