The NetBSD Project

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

[BACK] Up to [] / src / external / public-domain / sqlite / dist

Request diff between arbitrary revisions

Default branch: MAIN

Revision / (download) - annotate - [select for diffs] (vendor branch), Fri Mar 1 14:46:45 2024 UTC (31 minutes, 56 seconds ago) by christos
Branch: SQLITE
CVS Tags: sqlite-3-45-1
Changes since +9872 -4991 lines
Diff to previous (colored)

Import sqlite-3.45-1 (previous was 3.43.0)

SQLite Release 3.45.1 On 2024-01-30
Prior changes from version 3.45.0 (2024-01-15):

Added the SQLITE_RESULT_SUBTYPE property for application-defined
SQL functions. All application defined SQL functions that invokes
sqlite3_result_subtype() must be registered with this new property.
Failure to do so might cause the call to sqlite3_result_subtype()
to behave as a no-op. Compile with -DSQLITE_STRICT_SUBTYPE=1 to
cause an SQL error to be raised if a function that is not
SQLITE_RESULT_SUBTYPE tries invokes sqlite3_result_subtype(). The
use of -DSQLITE_STRICT_SUBTYPE=1 is a recommended compile-time
option for every application that makes use of subtypes.

Enhancements to the JSON SQL functions:
All JSON functions are rewritten to use a new internal parse tree
format called JSONB. The new parse-tree format is serializable and
hence can be stored in the database to avoid unnecessary re-parsing
whenever the JSON value is used.  New versions of JSON-generating
functions generate binary JSONB instead of JSON text.
The json_valid() function adds an optional second argument that
specifies what it means for the first argument to be "well-formed".
Add the FTS5 tokendata option to the FTS5 virtual table.
The SQLITE_DIRECT_OVERFLOW_READ optimization is now enabled by
default. Disable it at compile-time using -DSQLITE_DIRECT_OVERFLOW_READ=0.

Query planner improvements:
Do not allow the transitive constraint optimization to trick the
query planner into using a range constraint when a better equality
constraint is available. (Forum post 2568d1f6e6.)
The query planner now does a better job of disregarding indexes
that ANALYZE identifies as low-quality. (Forum post 6f0958b03b.)
Increase the default value for SQLITE_MAX_PAGE_COUNT from 1073741824
to 4294967294.

Enhancements to the CLI:
Improvements to the display of UTF-8 content on Windows
Automatically detect playback of ".dump" scripts and make appropriate
changes to settings such as ".dbconfig defensive off" and ".dbconfig
dqs_dll on".

Changes in this specific patch release, version 3.45.1 (2024-01-30):
Restore the JSON BLOB input bug, and promise to support the anomaly
in subsequent releases, for backward compatibility.
Fix the PRAGMA integrity_check command so that it works on read-only
databases that contain FTS3 and FTS5 tables. This resolves an issue
introduced in version 3.44.0 but was undiscovered until after the
3.45.0 release.

Fix issues associated with processing corrupt JSONB inputs:
Prevent exponential runtime when converting a corrupt JSONB into text.
Fix a possible read of one byte past the end of the JSONB blob when
converting a corrupt JSONB into text.
Enhanced testing using jfuzz to prevent any future JSONB problems
such as the above.
Fix a long-standing bug in which a read of a few bytes past the
end of a memory-mapped segment might occur when accessing a craftily
corrupted database using memory-mapped database.
Fix a long-standing bug in which a NULL pointer dereference might
occur in the bytecode engine due to incorrect bytecode being
generated for a class of SQL statements that are deliberately
designed to stress the query planner but which are otherwise

[for changes to previous releases see:]

Revision 1.22 / (download) - annotate - [select for diffs], Mon Sep 4 23:55:53 2023 UTC (5 months, 3 weeks ago) by christos
Branch: MAIN
Changes since 1.21: +10 -1 lines
Diff to previous 1.21 (colored)

fix the vax build. we could do better by choosing larger exponents.

Revision 1.21 / (download) - annotate - [select for diffs], Mon Sep 4 17:05:24 2023 UTC (5 months, 3 weeks ago) by christos
Branch: MAIN
Changes since 1.20: +61271 -31009 lines
Diff to previous 1.20 (colored)

merge conflicts between 3.26.0 and 3.34.0

Revision / (download) - annotate - [select for diffs] (vendor branch), Mon Sep 4 16:46:19 2023 UTC (5 months, 3 weeks ago) by christos
Branch: SQLITE
CVS Tags: sqlite-3-43-0
Changes since +61273 -31007 lines
Diff to previous (colored)

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 YYY-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
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
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.
SQLITE_SOURCE_ID: 2023-08-24 12:36:59
SHA3-256 for sqlite3.c:

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
Enhance the JSON SQL functions to support JSON5 extensions.
sqlite3_config() are now allowed to occur after sqlite3_initialize().
New sqlite3_db_config() options: SQLITE_DBCONFIG_STMT_SCANSTATUS
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
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,
Enhancements to PRAGMA integrity_check:
Detect and raise an error when a NaN value is stored in a NOT NULL
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
Miscellaneous bug fixes and performance optimizations
SQLITE_SOURCE_ID: 2023-05-16 12:36:15
SHA3-256 for sqlite3.c:

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()
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
Fix a few incorrect assert() statements.
SQLITE_SOURCE_ID: 2023-03-22 11:56:21
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2023-03-10 12:13:52
SHA3-256 for sqlite3.c:

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
The ".scanstats est" command provides query planner estimates in
The continuation prompt indicates if the input is currently inside
of a string literal, identifier literal, comment, trigger definition,
Enhance the --safe command-line option to disallow dangerous SQL
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()
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.
SQLITE_SOURCE_ID: 2023-02-21 18:09:37
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2022-12-28 14:03:47
SHA3-256 for sqlite3.c:

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
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.
SQLITE_SOURCE_ID: 2022-11-16 12:10:08
SHA3-256 for sqlite3.c:

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
SQLITE_SOURCE_ID: 2022-09-29 15:55:41
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2022-09-05 11:02:23
SHA3-256 for sqlite3.c:

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
Apply fixes for CVE-2022-35737, Chromium bugs 1343348 and 1345947,
forum post 3607259d3c, and other minor problems discovered by
internal testing.
SQLITE_SOURCE_ID: 2022-07-21 15:24:47
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2022-07-13 19:41:41
SHA3-256 for sqlite3.c:

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
SQLITE_SOURCE_ID: 2022-06-25 14:57:57
SHA3-256 for sqlite3.c:

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

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.
SQLITE_SOURCE_ID: 2022-05-04 15:45:55
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2022-04-27 12:03:15
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2022-03-26 13:51:10
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2022-03-12 13:37:29
SHA3-256 for sqlite3.c:

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
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
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
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
SQLITE_SOURCE_ID: 2022-02-22 18:58:40
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2022-01-06 13:25:41
SHA3-256 for sqlite3.c:

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
Improved robustness of the --safe option in the CLI.
Other minor fixes to assert() statements and test cases.
SQLITE_SOURCE_ID: 2021-12-30 15:30:28
SHA3-256 for sqlite3.c:

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
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
Added new sqlite3_changes64() and sqlite3_total_changes64()
Added the SQLITE_OPEN_EXRESCODE flag option to sqlite3_open_v2().
Use less memory to hold the database schema.
SQLITE_SOURCE_ID: 2021-11-27 14:13:22
SHA3-256 for sqlite3.c:

2021-06-18 (3.36.0)
Improvement to the EXPLAIN QUERY PLAN output to make it easier to
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
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.
SQLITE_SOURCE_ID: 2021-06-18 18:36:39
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2021-04-19 18:32:05
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2021-04-02 15:20:15
SHA3-256 for sqlite3.c:

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
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
SQLITE_SOURCE_ID: 2021-03-26 12:12:52
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2021-03-17 19:07:21
SHA3-256 for sqlite3.c:

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
SQLITE_SOURCE_ID: 2021-03-15 16:53:57
SHA3-256 for sqlite3.c:

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
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.
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
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
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
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.
SQLITE_SOURCE_ID: 2021-03-12 15:10:09
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2021-01-20 14:10:07
SHA3-256 for sqlite3.c:

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
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
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()
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.
SQLITE_SOURCE_ID: 2020-12-01 16:14:00
SHA3-256 for sqlite3.c:

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
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
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
SQLITE_SOURCE_ID: 2020-08-14 13:23:32
SHA3-256 for sqlite3.c:

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

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
SQLITE_SOURCE_ID: 2020-06-04 12:58:43
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2020-05-25 16:19:56
SHA3-256 for sqlite3.c:

2020-05-22 (3.32.0)
Added support for approximate ANALYZE using the PRAGMA analysis_limit
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
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
SHA3-256 for sqlite3.c:

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.
SQLITE_SOURCE_ID: 2020-01-27 19:55:54
SHA3-256 for sqlite3.c:

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,
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
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
Provide the ability to tag application-defined SQL functions with
Add new verbs to sqlite3_vtab_config() so that the xConnect method
of virtual tables can declare the virtual table as SQLITE_VTAB_INNOCUOUS
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
SQLITE_SOURCE_ID: 2020-01-22 18:38:59
SHA3-256 for sqlite3.c:

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
SQLITE_SOURCE_ID: 2019-10-10 20:19:45
SHA3-256 for sqlite3.c:

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
The index_info and index_xinfo pragmas are enhanced to provide
information about the on-disk representation of WITHOUT ROWID
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
The PRAGMA function_list, PRAGMA module_list, and PRAGMA pragma_list
commands are now enabled in all builds by default. Disable them
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.
SQLITE_SOURCE_ID: 2019-10-04 15:03:17
SHA3-256 for sqlite3.c:

2019-07-10 (3.29.0)
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
SQLITE_SOURCE_ID: 2019-07-10 17:32:03
SHA3-256 for sqlite3.c:

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 The Git mirror can be seen at
SQLITE_SOURCE_ID: 2019-04-16 19:49:53
SHA3-256 for sqlite3.c:

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
Fix various documentation typos
SHA3-256 for sqlite3.c:

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
SQLITE_SOURCE_ID: 2019-02-08 13:17:39
SHA3-256 for sqlite3.c:

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
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()
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
SQLITE_SOURCE_ID: "2019-02-07 17:02:52
SHA3-256 for sqlite3.c:

Revision 1.20 / (download) - annotate - [select for diffs], Fri Oct 30 12:32:04 2020 UTC (3 years, 4 months ago) by maya
Branch: MAIN
CVS Tags: netbsd-10-base, netbsd-10-0-RC5, netbsd-10-0-RC4, netbsd-10-0-RC3, netbsd-10-0-RC2, netbsd-10-0-RC1, netbsd-10, cjep_sun2x-base1, cjep_sun2x-base, cjep_sun2x, cjep_staticlib_x-base1, cjep_staticlib_x-base, cjep_staticlib_x
Changes since 1.19: +2 -2 lines
Diff to previous 1.19 (colored)

Use the same macro used before for avoiding too large floats on vax.

This has the advantage of not changing the number for non-vax, so is a
safer change for those architectures.
(Might not actually matter).

Revision 1.19 / (download) - annotate - [select for diffs], Fri Oct 30 06:02:05 2020 UTC (3 years, 4 months ago) by martin
Branch: MAIN
Changes since 1.18: +2 -2 lines
Diff to previous 1.18 (colored)

Instead of a random 'prohibitively high' value, use DBL_MAX so it builds on VAX

Revision / (download) - annotate - [select for diffs], Mon Jun 10 22:04:56 2019 UTC (4 years, 8 months ago) by christos
Branch: phil-wifi
Changes since 1.16: +37825 -18684 lines
Diff to previous 1.16 (colored) next main 1.17 (colored)

Sync with HEAD

Revision / (download) - annotate - [select for diffs], Wed Dec 26 14:01:18 2018 UTC (5 years, 2 months ago) by pgoyette
Branch: pgoyette-compat
CVS Tags: pgoyette-compat-merge-20190127
Changes since 1.16: +37825 -18684 lines
Diff to previous 1.16 (colored) next main 1.17 (colored)

Sync with HEAD, resolve a few conflicts

Revision 1.18 / (download) - annotate - [select for diffs], Sat Dec 22 03:22:19 2018 UTC (5 years, 2 months ago) by christos
Branch: MAIN
CVS Tags: phil-wifi-20200421, phil-wifi-20200411, phil-wifi-20200406, phil-wifi-20191119, phil-wifi-20190609, pgoyette-compat-20190127, pgoyette-compat-20190118, pgoyette-compat-1226, netbsd-9-base, netbsd-9-3-RELEASE, netbsd-9-2-RELEASE, netbsd-9-1-RELEASE, netbsd-9-0-RELEASE, netbsd-9-0-RC2, netbsd-9-0-RC1, netbsd-9, is-mlppp-base, is-mlppp
Changes since 1.17: +1 -2 lines
Diff to previous 1.17 (colored)

remove stray line

Revision 1.17 / (download) - annotate - [select for diffs], Wed Dec 19 22:21:13 2018 UTC (5 years, 2 months ago) by christos
Branch: MAIN
Changes since 1.16: +36034 -16892 lines
Diff to previous 1.16 (colored)

merge conflicts.

Revision / (download) - annotate - [select for diffs] (vendor branch), Wed Dec 19 19:56:48 2018 UTC (5 years, 2 months ago) by christos
Branch: SQLITE
CVS Tags: sqlite-3-26-0
Changes since +37815 -18684 lines
Diff to previous (colored)

SQLite Release 3.26.0 On 2018-12-01

 1. Optimization: When doing an UPDATE on a table with indexes on
    expressions, do not update the expression indexes if they do not
    refer to any of the columns of the table being updated.

 2. Allow the xBestIndex() method of virtual table implementations to
    return SQLITE_CONSTRAINT to indicate that the proposed query plan
    is unusable and should not be given further consideration.

 3. Added the SQLITE_DBCONFIG_DEFENSIVE option which disables the
    ability to create corrupt database files using ordinary SQL.

 4. Added support for read-only shadow tables when the
    SQLITE_DBCONFIG_DEFENSIVE option is enabled.

 5. Added the PRAGMA legacy_alter_table command, which if enabled
    causes the ALTER TABLE command to behave like older version of
    SQLite (prior to version 3.25.0) for compatibility.

 6. Added PRAGMA table_xinfo that works just like PRAGMA table_info
    except that it also shows hidden columns in virtual tables.

 7. Added the explain virtual table as a run-time loadable extension.

 8. Add a limit counter to the query planner to prevent excessive
    sqlite3_prepare() times for certain pathological SQL inputs.

 9. Added support for the sqlite3_normalized_sql() interface, when
    compiling with SQLITE_ENABLE_NORMALIZE.

10. Enhanced triggers so that they can use table-valued functions
    that exist in schemas other than the schema where the trigger is

11. Enhancements to the CLI:
    a. Improvements to the ".help" command.
    b. The SQLITE_HISTORY environment variable, if it exists,
       specifies the name of the command-line editing history file
    c. The --deserialize option associated with opening a new
       database cause the database file to be read into memory and
       accessed using the sqlite3_deserialize() API. This simplifies
       running tests on a database without modifying the file on disk.

12. Enhancements to the geopoly extension:
    a. Always stores polygons using the binary format, which is
       faster and uses less space.
    b. Added the geopoly_regular() function.
    c. Added the geopoly_ccw() function.

13. Enhancements to the session extension:
    b. Added the sqlite3changeset_start_v2() interface and the
    c. Added the changesetfuzz.c test-case generator utility.

Revision / (download) - annotate - [select for diffs], Fri Apr 21 16:53:01 2017 UTC (6 years, 10 months ago) by bouyer
Branch: bouyer-socketcan
Changes since 1.15: +11185 -6630 lines
Diff to previous 1.15 (colored) next main 1.16 (colored)

Sync with HEAD

Revision / (download) - annotate - [select for diffs], Mon Mar 20 06:56:50 2017 UTC (6 years, 11 months ago) by pgoyette
Branch: pgoyette-localcount
Changes since +11185 -6630 lines
Diff to previous (colored) to branchpoint 1.14 (colored) next main 1.15 (colored)

Sync with HEAD

Revision 1.16 / (download) - annotate - [select for diffs], Sat Mar 11 16:29:51 2017 UTC (6 years, 11 months ago) by christos
Branch: MAIN
CVS Tags: prg-localcount2-base3, prg-localcount2-base2, prg-localcount2-base1, prg-localcount2-base, prg-localcount2, phil-wifi-base, pgoyette-localcount-20170426, pgoyette-localcount-20170320, pgoyette-compat-base, pgoyette-compat-1126, pgoyette-compat-1020, pgoyette-compat-0930, pgoyette-compat-0906, pgoyette-compat-0728, pgoyette-compat-0625, pgoyette-compat-0521, pgoyette-compat-0502, pgoyette-compat-0422, pgoyette-compat-0415, pgoyette-compat-0407, pgoyette-compat-0330, pgoyette-compat-0322, pgoyette-compat-0315, perseant-stdc-iso10646-base, perseant-stdc-iso10646, netbsd-8-base, netbsd-8-2-RELEASE, netbsd-8-1-RELEASE, netbsd-8-1-RC1, netbsd-8-0-RELEASE, netbsd-8-0-RC2, netbsd-8-0-RC1, netbsd-8, matt-nb8-mediatek-base, matt-nb8-mediatek, bouyer-socketcan-base1
Branch point for: phil-wifi, pgoyette-compat
Changes since 1.15: +11191 -6636 lines
Diff to previous 1.15 (colored)

merge 3.17.0

Revision / (download) - annotate - [select for diffs] (vendor branch), Sat Mar 11 16:06:39 2017 UTC (6 years, 11 months ago) by christos
Branch: SQLITE
CVS Tags: sqlite-3-17-0
Changes since +11181 -6621 lines
Diff to previous (colored)

2017-02-13 (3.17.0)

Approximately 25% better performance from the R-Tree extension.
Uses compiler built-ins (ex: __builtin_bswap32() or _byteswap_ulong()) for byteswapping when available.
Uses the sqlite3_blob key/value access object instead of SQL for pulling content out of R-Tree nodes
Other miscellaneous enhancements such as loop unrolling.
Add the SQLITE_DEFAULT_LOOKASIDE compile-time option.
Increase the default lookaside size from 512,125 to 1200,100 as this provides better performance while only adding 56KB of extra memory per connection. Memory-sensitive applications can restore the old default at compile-time, start-time, or run-time.
Use compiler built-ins __builtin_sub_overflow(), __builtin_add_overflow(), and __builtin_mul_overflow() when available. (All compiler built-ins can be omitted with the SQLITE_DISABLE_INTRINSIC compile-time option.)
Added the SQLITE_ENABLE_NULL_TRIM compile-time option, which can result in significantly smaller database files for some applications, at the risk of being incompatible with older versions of SQLite.
Change SQLITE_DEFAULT_PCACHE_INITSZ from 100 to 20, for improved performance.
Added the SQLITE_UINT64_TYPE compile-time option as an analog to SQLITE_INT64_TYPE.
Perform some UPDATE operations in a single pass instead of in two passes.
Enhance the session extension to support WITHOUT ROWID tables.
Fixed performance problems and potential stack overflows when creating views from multi-row VALUES clauses with hundreds of thousands of rows.
Added the sha1.c extension.
In the command-line shell, enhance the ".mode" command so that it restores the default column and row separators for modes "line", "list", "column", and "tcl".
Enhance the SQLITE_DIRECT_OVERFLOW_READ option so that it works in WAL mode as long as the pages being read are not in the WAL file.
Enhance the LEMON parser generator so that it can store the parser object as a stack variable rather than allocating space from the heap and make use of that enhancement in the amalgamation.
Other performance improvements. Uses about 6.5% fewer CPU cycles.
Bug Fixes:

Throw an error if the ON clause of a LEFT JOIN references tables to the right of the ON clause. This is the same behavior as PostgreSQL. Formerly, SQLite silently converted the LEFT JOIN into an INNER JOIN. Fix for ticket 25e335f802dd.
Use the correct affinity for columns of automatic indexes. Ticket 7ffd1ca1d2ad4ec.
Ensure that the sqlite3_blob_reopen() interface can correctly handle short rows. Fix for ticket e6e962d6b0f06f46e.

SQLITE_SOURCE_ID: "2017-02-13 16:02:40 ada05cfa86ad7f5645450ac7a2a21c9aa6e57d2c"
SHA1 for sqlite3.c: cc7d708bb073c44102a59ed63ce6142da1f174d1
2017-01-06 (3.16.2)

Fix the REPLACE statement for WITHOUT ROWID tables that lack secondary indexes so that it works correctly with triggers and foreign keys. This was a new bug caused by performance optimizations added in version 3.16.0. Ticket 30027b613b4
Fix the sqlite3_value_text() interface so that it correctly translates content generated by zeroblob() into a string of all 0x00 characters. This is a long-standing issue discovered after the 3.16.1 release by OSS-Fuzz
Fix the bytecode generator to deal with a subquery in the FROM clause that is itself a UNION ALL where one side of the UNION ALL is a view that contains an ORDER BY. This is a long-standing issue that was discovered after the release of 3.16.1. See ticket 190c2507.
Adjust the sqlite3_column_count() API so it more often returns the same values for PRAGMA statements as it did in prior releases, to minimize disruption to applications that might be using that interface in unexpected ways.

SQLITE_SOURCE_ID: "2017-01-06 16:32:41 a65a62893ca8319e89e48b8a38cf8a59c69a8209"
SHA1 for sqlite3.c: 2bebdc3f24911c0d12b6d6c0123c3f84d6946b08
2017-01-03 (3.16.1)

Fix a bug concerning the use of row values within triggers (see ticket 8c9458e7) that was in version 3.15.0 but was not reported until moments after the 3.16.0 release was published.

SQLITE_SOURCE_ID: "2017-01-03 18:27:03 979f04392853b8053817a3eea2fc679947b437fd"
SHA1 for sqlite3.c: 354f6223490b30fd5320b4066b1535e4ce33988d
2017-01-02 (3.16.0)

Uses 9% fewer CPU cycles. (See the CPU performance measurement report for details on how this performance increase was computed.)
Added experimental support for PRAGMA functions.
Added the SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE option to sqlite3_db_config().
Enhance the date and time functions so that the 'unixepoch' modifier works for the full span of supported dates.
Changed the default configuration of the lookaside memory allocator from 500 slots of 128 bytes each into 125 slots of 512 bytes each.
Enhanced "WHERE x NOT NULL" partial indexes so that they are usable if the "x" column appears in a LIKE or GLOB operator.
Enhanced sqlite3_interrupt() so that it interrupts checkpoint operations that are in process.
Enhanced the LIKE and GLOB matching algorithm to be faster for cases when the pattern contains multiple wildcards.
Added the SQLITE_FCNTL_WIN32_GET_HANDLE file control opcode.
Added ".mode quote" to the command-line shell.
Added ".lint fkey-indexes" to the command-line shell.
Added the .imposter dot-command to the command-line shell.
Added the remember(V,PTR) SQL function as a loadable extension.
Rename the SQLITE_OMIT_BUILTIN_TEST compile-time option to SQLITE_UNTESTABLE to better reflect the implications of using it.
Bug Fixes:

Fix a long-standing bug in the query planner that caused incorrect results on a LEFT JOIN where the left-hand table is a subquery and the join constraint is a bare column name coming from the left-hand subquery. Ticket 2df0107b.
Correctly handle the integer literal -0x8000000000000000 in the query planner.

SQLITE_SOURCE_ID: "2017-01-02 11:57:58 04ac0b75b1716541b2b97704f4809cb7ef19cccf"
SHA1 for sqlite3.c: e2920fb885569d14197c9b7958e6f1db573ee669
2016-11-28 (3.15.2)

Multiple bug fixes to the row value logic that was introduced in version 3.15.0.
Fix a NULL pointer dereference in ATTACH/DETACH following a maliciously constructed syntax error. Ticket 2f1b168ab4d4844.
Fix a crash that can occur following an out-of-memory condition in the built-in instr() function.
In the JSON extension, fix the JSON validator so that it correctly rejects invalid backslash escapes within strings.

SQLITE_SOURCE_ID: "2016-11-28 19:13:37 bbd85d235f7037c6a033a9690534391ffeacecc8"
SHA1 for sqlite3.c: 06d77b42a3e70609f8d4bbb97caf53652f1082cb
2016-11-04 (3.15.1)

Added SQLITE_FCNTL_WIN32_GET_HANDLE file control opcode.
Fix the VACUUM command so that it spills excess content to disk rather than holding everything in memory, and possible causing an out-of-memory error for larger database files. This fixes an issue introduced by version 3.15.0.
Fix a case (present since 3.8.0 - 2013-08-26) where OR-connected terms in the ON clause of a LEFT JOIN might cause incorrect results. Ticket 34a579141b2c5ac.
Fix a case where the use of row values in the ON clause of a LEFT JOIN might cause incorrect results. Ticket fef4bb4bd9185ec8f.

SQLITE_SOURCE_ID: "2016-11-04 12:08:49 1136863c76576110e710dd5d69ab6bf347c65e36"
SHA1 for sqlite3.c: e7c26a7be3e431dd06898f8d262c4ef240c07366
2016-10-14 (3.15.0)

Added support for row values.
Allow deterministic SQL functions in the WHERE clause of a partial index.
Added the "modeof=filename" URI parameter on the unix VFS
Added the ability to VACUUM an ATTACH-ed database.
Enhancements to the command-line shell:
Add the ".testcase" and ".check" dot-commands.
Added the --new option to the ".open" dot-command, causing any prior content in the database to be purged prior to opening.
Enhance the fts5vocab virtual table to handle "ORDER BY term" efficiently.
Miscellaneous micro-optimizations reduce CPU usage by more than 7% on common workloads. Most optimization in this release has been on the front-end (sqlite3_prepare_v2()).
Bug Fixes:

The multiply operator now correctly detects 64-bit integer overflow and promotes to floating point in all corner-cases. Fix for ticket 1ec41379c9c1e400.
Correct handling of columns with redundant unique indexes when those columns are used on the LHS of an IN operator. Fix for ticket 0eab1ac759.
Skip NULL entries on range queries in indexes on expressions. Fix for ticket 4baa46491212947.
Ensure that the AUTOINCREMENT counters in the sqlite_sequence table are initialized doing "Xfer Optimization" on "INSERT ... SELECT" statements. Fix for ticket 7b3328086a5c116c.
Make sure the ORDER BY LIMIT optimization (from check-in 559733b09e) works with IN operators on INTEGER PRIMARY KEYs. Fix for ticket 96c1454c

SQLITE_SOURCE_ID: "2016-10-14 10:20:30 707875582fcba352b4906a595ad89198d84711d8"
SHA1 for sqlite3.c: fba106f8f6493c66eeed08a2dfff0907de54ae76
2016-09-12 (3.14.2)

Improved support for using the STDCALL calling convention in winsqlite3.dll.
Fix the sqlite3_trace_v2() interface so that it is disabled if either the callback or the mask arguments are zero, in accordance with the documentation.
Fix commenting errors and improve the comments generated on EXPLAIN listings when the -DSQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option is used.
Fix the ".read" command in the command-line shell so that it understands that its input is not interactive.
Correct affinity computations for a SELECT on the RHS of an IN operator. Fix for ticket 199df4168c.
The ORDER BY LIMIT optimization is not valid unless the inner-most IN operator loop is actually used by the query plan. Fix for ticket 0c4df46116e90f92.
Fix an internal code generator problem that was causing some DELETE operations to no-op. Ticket ef360601

SQLITE_SOURCE_ID: "2016-09-12 18:50:49 29dbef4b8585f753861a36d6dd102ca634197bd6"
SHA1 for sqlite3.c: bcc4a1989db45e7f223191f2d0f66c1c28946383
2016-08-11 (3.14.1)

A performance enhancement to the page-cache "truncate" operation reduces COMMIT time by dozens of milliseconds on systems with a large page cache.
Fix to the --rbu option of sqldiff.

SQLITE_SOURCE_ID: "2016-08-11 18:53:32 a12d8059770df4bca59e321c266410344242bf7b"
SHA1 for sqlite3.c: d545b24892278272ce4e40e0567d69c8babf12ea
2016-08-08 (3.14)

Celebrating the SQLite "# release" with a home-baked pie.
Added support for WITHOUT ROWID virtual tables.
Improved the query planner so that the OR optimization can be used on virtual tables even if one or more of the disjuncts use the LIKE, GLOB, REGEXP, MATCH operators.
Added the CSV virtual table for reading RFC 4180 formatted comma-separated value files.
Added the carray() table-valued function extension.
Enabled persistent loadable extensions using the new SQLITE_OK_LOAD_PERMANENTLY return code from the extension entry point.
Added the SQLITE_DBSTATUS_CACHE_USED_SHARED option to sqlite3_db_status().
Add the vfsstat.c loadable extension - a VFS shim that measures I/O together with an eponymous virtual table that provides access to the measurements.
Improved algorithm for running queries with both an ORDER BY and a LIMIT where only the inner-most loop naturally generates rows in the correct order.
Enhancements to Lemon parser generator, so that it generates a faster parser.
The PRAGMA compile_options command now attempts to show the version number of the compiler that generated the library.
Enhance PRAGMA table_info so that it provides information about eponymous virtual tables.
Added the "win32-none" VFS, analogous to the "unix-none" VFS, that works like the default "win32" VFS except that it ignores all file locks.
The query planner uses a full scan of a partial index instead of a full scan of the main table, in cases where that makes sense.
Allow table-valued functions to appear on the right-hand side of an IN operator.
Created the dbhash.exe command-line utility.
Added two new C-language interfaces: sqlite3_expanded_sql() and sqlite3_trace_v2(). These new interfaces subsume the functions of sqlite3_trace() and sqlite3_profile() which are now deprecated.
Added the json_quote() SQL function to the json1 extension.
Disable the authorizer callback while reparsing the schema.
Added the SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION compile-time option and turned that option on by default when building the command-line shell.
Bug Fixes:

Fix the ALTER TABLE command so that it does not corrupt descending indexes when adding a column to a legacy file format database. Ticket f68bf68513a1c15f
Fix a NULL-pointer dereference/crash that could occurs when a transitive WHERE clause references a non-existent collating sequence. Ticket e8d439c77685eca6.
Improved the cost estimation for an index scan which includes a WHERE clause that can be partially or fully evaluated using columns in the index and without having to do a table lookup. This fixes a performance regression that occurred for some obscure queries following the ORDER BY LIMIT optimization introduced in version 3.12.0.

SQLITE_SOURCE_ID: "2016-08-08 13:40:27 d5e98057028abcf7217d0d2b2e29bbbcdf09d6de"
SHA1 for sqlite3.c: 234a3275d03a287434ace3ccdf1afb208e6b0e92

Revision / (download) - annotate - [select for diffs], Fri Nov 4 14:48:50 2016 UTC (7 years, 3 months ago) by pgoyette
Branch: pgoyette-localcount
Changes since 1.14: +18 -10 lines
Diff to previous 1.14 (colored)

Sync with HEAD

Revision 1.15 / (download) - annotate - [select for diffs], Thu Oct 13 18:11:19 2016 UTC (7 years, 4 months ago) by martin
Branch: MAIN
CVS Tags: pgoyette-localcount-20170107, pgoyette-localcount-20161104, bouyer-socketcan-base
Branch point for: bouyer-socketcan
Changes since 1.14: +18 -10 lines
Diff to previous 1.14 (colored)

PR lib/51533: make big endian arm support work again, patch from
Rin Okuyama.

Revision 1.14 / (download) - annotate - [select for diffs], Mon Jul 4 03:04:25 2016 UTC (7 years, 7 months ago) by abhinav
Branch: MAIN
CVS Tags: pgoyette-localcount-base, pgoyette-localcount-20160806, pgoyette-localcount-20160726, localcount-20160914
Branch point for: pgoyette-localcount
Changes since 1.13: +2 -2 lines
Diff to previous 1.13 (colored)

Use constant.
This change was lost while resolving merge conflict as the lines had moved around too much.

Revision 1.13 / (download) - annotate - [select for diffs], Sun Jul 3 10:23:30 2016 UTC (7 years, 7 months ago) by abhinav
Branch: MAIN
Changes since 1.12: +93854 -42756 lines
Diff to previous 1.12 (colored)

Merge conflicts for sqlite-3.13.0

Revision / (download) - annotate - [select for diffs] (vendor branch), Sun Jul 3 09:24:37 2016 UTC (7 years, 7 months ago) by abhinav
Branch: SQLITE
CVS Tags: sqlite-3-13-0
Changes since +93316 -42216 lines
Diff to previous (colored)

Import sqlite-3.13.0.
Following changes have been made since the last import (taken from

2016-05-18 - Release 3.13.0

SQLite version 3.13.0 is a regularly schedule maintenance release containg
performance enhancements and fixes for obscure bugs.
2016-04-18 - Release 3.12.2

Yikes! The 3.12.0 and 3.12.1 releases contain a backwards compatibility bug!
Tables that declare a column with type "INTEGER" PRIMARY KEY (where the
datatype name INTEGER is quoted) generate an incompatible database file. The
mistake came about because the developers have never thought to put a typename
in quotes before, and so there was no documentation of that capability nor any
tests. (There are tests now, though, of course.) Instances of quoting the
datatype name are probably infrequent in the wild, so we do not expect the
impact of this bug to be too severe. Upgrading is still strongly recommended.

Fixes for three other minor issues were included in this patch release. The
other issues would have normally been deferred until the next scheduled
release, but since a patch release is being issued anyhow, they might as well
be included.

2016-04-08 - Release 3.12.1

SQLite version 3.12.1 is an emergency patch release to address a crash bug that
snuck into version 3.12.0. Upgrading from version 3.12.0 is highly recommended.

Another minor problem involving datatypes on view columns, and a query planner
deficiency are fixed at the same time. These two issues did not justify a new
release on their own, but since a release is being issued to deal with the
crash bug, we included these other fixes for good measure.

2016-03-29 - Release 3.12.0

SQLite version 3.12.0 is a regularly scheduled maintenance release. A notable
change in this release is an increase in the default page size for newly
created database files. There are also various performance improvements. See
the change log for details.

2016-03-03 - Release 3.11.1

SQLite version 3.11.1 is a patch release that fixes problems in the new FTS5
extension and increases a default setting in the spellfix1 extension, and
implements enhancements to some of the Windows makefiles. The SQLite core is
unchanged from 3.11.0. Upgrading is optional.

2016-02-15 - Release 3.11.0

SQLite version 3.11.0 is a regularly scheduled maintenance release.

2016-01-20 - Release 3.10.2

Yikes! An optimization attempt gone bad resulted in a bug in the LIKE operator
which is fixed by this patch release. Three other minor but low-risk fixes are
also included in the patch.

2016-01-14 - Release 3.10.1

SQLite version 3.10.1 is a bug-fix release primarily targeting the fix for the
query planner bug cb3aa0641d9a4 discovered by Mapscape. Also included is a
minor API enhancement requested by the Firefox developers at Mozilla. The
differences from version 3.10.0 are minimal.

2016-01-06 - Release 3.10.0

SQLite version 3.10.0 is a regularly scheduled maintenance release.

2015-11-02 - Release 3.9.2

SQLite version 3.9.2 is a patch release fixing two obscure bugs. (Details: (1),
(2)). Upgrade only if you are having problems.

2015-10-16 - Release 3.9.1

SQlite version 3.9.1 is a small patch to version 3.9.0 that includes a few
simple build script and #ifdef tweaks to make the code easier to compile on a
wider variety of platform. There are no functional changes, except for a single
minor bug-fix in the json1 extension to stop it from recognizing form-feed
(ASCII 0x0c) as a whitespace character, in conformance with RFC7159.

2015-10-14 - Release 3.9.0

SQLite version 3.9.0 is a regularly schedule maintenance release. Key changes

Begin using semantic versioning.
JSON SQL functions
The FTS5 full-text search engine
Support for indexes on expressions
Support for table-valued functions
See the change log for a long and more complete list of changes.
2015-07-29 - Release

SQLite version is a patch release that fixes two arcane issues that
were reported shortly after 3.8.11 was released. Upgrade from 3.8.11 only in
the unlikely event that one of these obscure issues affect your code.

2015-07-27 - Release 3.8.11

SQLite version 3.8.11 is a regularly scheduled maintenance release. See the
change log for details.

2015-05-20 - Release

Yikes! Index corruption after a sequence of valid SQL statements!

It has been many years since anything like this bug has snuck into an official
SQLite release. But for the pasts seven months (version 3.8.7 through version if you do an INSERT into a carefully crafted schema in which there
are two nested triggers that convert an index key value from TEXT to INTEGER
and then back to TEXT again, the INTEGER value might get inserted as the index
key instead of the correct TEXT, resulting in index corruption. This patch
release adds a single line of code to fix the problem.

If you do actually encounter this problem, running REINDEX on the damaged
indexes will clear it.

2015-05-09 - Release

The 3.8.10 release did not add the new SQLITE_ENABLE_DBSTAT_VTAB compile-time
option to the sqlite3_compileoption_used() interface. This patch release fixes
that omission. And while we are at it, the associated dbstat virtual table was
enhanced slightly and a harmless compiler warning was fixed.

There is no reason to upgrade from version 3.8.10 unless you are using the new
SQLITE_ENABLE_DBSTAT_VTAB compile-time option.

2015-05-07 - Release 3.8.10

SQLite version 3.8.10 is a regularly scheduled maintenance release. This
release features performance improvements, fixes to several arcane bugs found
by the AFL fuzzer, the new "sqldiff.exe" command-line utility, improvements to
the documentation, and other enhancements. See the release notes for additional

2015-04-08 - Release 3.8.9

SQLite version 3.8.9 is a regularly scheduled maintenance release. New features
in this release include the PRAGMA index_xinfo command, the sqlite3_status64()
interface, and the ".dbinfo" command of the command-line shell. See the release
notes for additional information.

2015-02-25 - Release

The patch release fixes an obscure problem in the SQLite code generator
that can cause incorrect results when the qualifying expression of a partial
index is used inside the ON clause of a LEFT JOIN. This problem has been in the
code since support for partial indexes was first added in version 3.8.0.
However, it is difficult to imagine a valid reason to every put the qualifying
constraint inside the ON clause of a LEFT JOIN, and so this issue has never
come up before.

Any applications that is vulnerable to this bug would have encountered problems
already. Hence, upgrading from the previous release is optional.

2015-01-30 - Release

The patch release fixes a single minor problem: It ensures that the
sqlite3_wal_checkpoint(TRUNCATE) operation will always truncate the write-ahead
log even if log had already been reset and contained no new content. It is
unclear if this is a bug fix or a new feature.

Something like this would normally go into the next regularly scheduled
release, but a prominent SQLite user needed the change in a hurry so we were
happy to rush it out via this patch.

There is no reason to upgrade unless you actually need the enhanced behavior of

2015-01-20 - Release

Within hours of releasing version 3.8.8, a bug was reported against the
10-month-old 3.8.4 release. As that bug exists in all subsequent releases, the
decision was made to issue a small patch to the 3.8.8 before it came into
widespread use.

See ticket f97c4637102a3ae72b7911 for a description of the bug.

The changes between versions 3.8.8 and are minimal.

2015-01-16 - Release 3.8.8

SQLite version 3.8.8 is a regularly schedule maintenance release of SQLite.

There are no dramatic new features or performance enhancements in this release,
merely incremental improvements. Most of the performance gain in this release
comes from refactoring the B-Tree rebalancing logic to avoid unnecessary
memcpy() operations. New features include the PRAGMA data_version statement and
the ability to accept a VALUES clause with no arbitrary limit on the number of
rows. Several obscure bugs have been fixed, including some multithreading races
and a work-around for a compiler bug on some Macs.

See the change log for a longer list of enhancements and bug fixes.

2014-12-09 - Release

SQLite version an unscheduled bug-fix release. Changes from the
previous release and from version 3.8.7 are minimal.

This release fixes adds in a mutex that is required by the changes of the patch but was accidentally omitted. The mutex was not required by any
of the internal SQLite tests, but Firefox crashes without it. Test cases have
been added to ensure that mutex is never again missed.

2014-12-06 - Release

SQLite version an unscheduled bug-fix release. Changes from the
previous release and from version 3.8.7 are minimal.

This release fixes two obscure bugs that can result in incorrect query results
and/or application crashes, but not (as far as we can tell) security
vulnerabilities. Both bugs have been latent in the code across multiple prior
releases and have never before been encountered, so they are unlikely to cause
problems. Nevertheless it seems prudent to publish fixes for them both. See the
change log for details.

2014-11-19 - Release

SQLite version is a patch and bug-fix release. Changes from the
previous release are minimal.

The primary reason for this release is to enhance the ROLLBACK command so that
it allows running queries on the same database connection to continue running
as long as the ROLLBACK does not change the schema. In all previous versions of
SQLite, a ROLLBACK would cause pending queries to stop immediately and return
SQLITE_ABORT or SQLITE_ABORT_ROLLBACK. Pending queries still abort if the
ROLLBACK changes the database schema, but as of this patch release, the queries
are allowed to continue running if the schema is unmodified.

In addition to the ROLLBACK enhancement, this patch release also includes fixes
for three obscure bugs. See the change log for details.

2014-10-30 - Release

SQLite version is a bug-fix release.

The primary reason for this bug-fix release is to address a problem with
updating the value of fields at the end of a table that were added using ALTER
TABLE ADD COLUMN. This problem 1 first appeared in the 3.8.7 release.

Another minor annoyance in the 3.8.7 release was the fact that the Android
build tried to use the strchrnul() function from the standard C library but
that function is not available on Android. Android builds had to add
-DHAVE_STRCHRNUL=0 to work around the problem. This patch fixes that so that
Android builds should now work without any changes.

The operation of PRAGMA journal_mode=TRUNCATE has been enhanced so that it
invokes fsync() after truncating the journal file when PRAGMA synchronous=FULL.
This helps to preserve transaction durability in the case of a power loss
occurring shortly after commit.

Finally, a couple of long-standing and obscure problems associated with run
UPDATE and DELETE on VIEWs were fixed.

The changes from 3.8.7 are minimal.

2014-10-17 - Release 3.8.7

SQLite version 3.8.7 is a regularly scheduled maintenance release. Upgrading
from all prior versions is recommended.

Most of the changes from the previous release have been micro-optimizations
designed to help SQLite run a little faster. Each individual optimization has
an unmeasurably small performance impact. But the improvements add up. Measured
on a well-defined workload (which the SQLite developers use as a proxy for a
typical application workload) using cachegrind on Linux and compiled with gcc
4.8.1 and -Os on x64 linux, the current release does over 20% more work for the
same number of CPU cycles compared to the previous release. Cachegrind is not a
real CPU, and the workload used for measurement is only a proxy. So your
performance may vary. We expect to see about half the measured and reported
improvement in real-world applications. 10% is less than 20% but it is still
pretty good, we think.

This release includes a new set of C-language interfaces that have unsigned
64-bit instead of signed 32-bit length parameters. The new APIs do not provide
any new capabilities. But they do make it easier to write applications that are
more resistant to integer overflow vulnerabilities.

This release also includes a new sorter that is able to use multiple threads to
help with large sort operations. (Sort operations are sometimes required to
implement ORDER BY and/or GROUP BY clauses and are almost always required for
CREATE INDEX.) The multi-threads sorter is turned off by default and must be
enabled using the PRAGMA threads SQL command. Note that the multi-threaded
sorter provides faster real-time performance for large sorts, but it also uses
more CPU cycles and more energy.

2014-08-15 - Release 3.8.6

SQLite version 3.8.6 is a regularly scheduled maintenance release. Upgrading
from all previous versions is recommended.

This release contains the usual assortment of obscure bug fixes. One bug,
however, deserves special attention. A problem appeared in the CREATE INDEX
command beginning with version 3.8.2 (2013-12-06) that allowed, under some
circumstances, a UNIQUE index to be created on a column that was not unique.
Once the index was created, no new non-unique entries could be inserted, but
preexisting non-unique entries would remain. See ticket 9a6daf340df99ba93c for
further information. In addition to fixing this bug, the PRAGMA integrity_check
command has been enhanced to detect non-uniqueness in UNIQUE indices, so that
if this bug did introduce any problems in databases, those problems can be
easily detected.

Other noteworthy changes include the addition of support for hexadecimal
integers (ex: 0x1234), and performance enhancements to the IN operator which,
according to mailing list reports, help some queries run up to five times

Version 3.8.6 uses 25% fewer CPU cycles than version 3.8.0 from approximately
one year ago, according to valgrind and the test/speedtest1.c test program. On
the other hand, the compiled binary for version 3.8.6 is about 5% larger than
3.8.0. The size increase is due in part to the addition of new features such as
WITHOUT ROWID tables and common table expressions.

2014-06-04 - Release 3.8.5

SQLite version 3.8.5 is a regularly scheduled maintenance release. Upgrading
from the previous version is recommended.

Version 3.8.5 fixes more than a dozen obscure bugs. None of these bugs should
be a problem for existing applications. Nor do any of the bugs represent a
security vulnerability. Nevertheless, upgrading is recommended to prevent
future problems.

In addition to bug fixes, the 3.8.5 release adds improvements to the query
planner, especially regarding sorting using indices and handling OR terms in
the WHERE clause for WITHOUT ROWID tables. The ".system" and ".once"
dot-commands were added to the command-line interface. And there were
enhancements to the FTS4 and RTREE virtual tables. See the change log for

2014-04-03 - Release

The optimizations added in version 3.8.4 caused some queries that involve
subqueries in the FROM clause, DISTINCT, and ORDER BY clauses, to give an
incorrect result. See ticket 98825a79ce145 for details. This release adds a
one-character change to a single line of code to fix the problem.

2014-03-26 - Release

The code changes that resulted in the performance improvements in version 3.8.4
missed a single buffer overflow test, which could result in a read past the end
of a buffer while searching a database that is corrupted in a particular way.
Version fixes that problem using a one-line patch.

We are not aware of any problems in version 3.8.4 when working with well-formed
database files. The problem fixed by this release only comes up when reading
corrupt database files.

2014-03-11 - Release

SQLite version is a patch against version 3.8.4 that fixes two minor

Work around a C-preprocessor macro conflict that causes compilation problems
for some configurations of Visual Studio.
Adjust the cost computation for the skip-scan optimization for improved
Both of these issues came to light within minutes of tagging the previous
release. Neither issue is serious but they can be annoying. Hence, the decision
was made to do a quick patch release to address both issues.
2014-03-10 - Release 3.8.4

SQLite version 3.8.4 is a maintenance release featuring performance
enhancements and fixes for a number of obscure bugs. There are no significant
new features in SQLite version 3.8.4. However, the number of CPU cycles
(measured by valgrind) needed to do many common operations has be reduced by
about 12% relative to the previous release, and by about 25% relative to
version 3.7.16 from approximately one year ago.

Version 3.8.4 of SQLite fixes several corner-case bugs that were found since
the previous release. These bugs were unlikely to appear in practice, and none
represent a security vulnerability. Nevertheless, developers are encouraged to
upgrade from all prior releases.

Revision / (download) - annotate - [select for diffs], Wed Aug 20 00:00:16 2014 UTC (9 years, 6 months ago) by tls
Branch: tls-maxphys
Changes since 1.6: +53184 -41030 lines
Diff to previous 1.6 (colored) next main 1.7 (colored)

Rebase to HEAD as of a few days ago.

Revision / (download) - annotate - [select for diffs], Thu May 22 14:10:02 2014 UTC (9 years, 9 months ago) by yamt
Branch: yamt-pagecache
Changes since +53184 -41030 lines
Diff to previous (colored) to branchpoint (colored) next main (colored)

sync with head.

for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.

this commit was splitted into small chunks to avoid
a limitation of cvs.  ("Protocol error: too many arguments")

Revision 1.12 / (download) - annotate - [select for diffs], Wed Mar 12 20:00:22 2014 UTC (9 years, 11 months ago) by martin
Branch: MAIN
CVS Tags: yamt-pagecache-base9, tls-maxphys-base, tls-earlyentropy-base, tls-earlyentropy, riastradh-xf86-video-intel-2-7-1-pre-2-21-15, riastradh-drm2-base3, netbsd-7-nhusb-base-20170116, netbsd-7-nhusb-base, netbsd-7-nhusb, netbsd-7-base, netbsd-7-2-RELEASE, netbsd-7-1-RELEASE, netbsd-7-1-RC2, netbsd-7-1-RC1, netbsd-7-1-2-RELEASE, netbsd-7-1-1-RELEASE, netbsd-7-1, netbsd-7-0-RELEASE, netbsd-7-0-RC3, netbsd-7-0-RC2, netbsd-7-0-RC1, netbsd-7-0-2-RELEASE, netbsd-7-0-1-RELEASE, netbsd-7-0, netbsd-7
Changes since 1.11: +9 -1 lines
Diff to previous 1.11 (colored)

Try to avoid using float constants out of range

Revision 1.11 / (download) - annotate - [select for diffs], Mon Feb 17 19:30:12 2014 UTC (10 years ago) by christos
Branch: MAIN
Changes since 1.10: +1 -1 lines
Diff to previous 1.10 (colored)

use the constant definition

Revision 1.10 / (download) - annotate - [select for diffs], Mon Feb 17 12:06:15 2014 UTC (10 years ago) by martin
Branch: MAIN
Changes since 1.9: +1 -1 lines
Diff to previous 1.9 (colored)

Fix bogus #ifdef __vax__

Revision 1.9 / (download) - annotate - [select for diffs], Sun Feb 16 18:09:43 2014 UTC (10 years ago) by christos
Branch: MAIN
Changes since 1.8: +58390 -46244 lines
Diff to previous 1.8 (colored)

merge conflicts.

Revision / (download) - annotate - [select for diffs] (vendor branch), Sun Feb 16 18:04:37 2014 UTC (10 years ago) by christos
Branch: SQLITE
CVS Tags: sqlite-3-8-3-1
Changes since +53167 -41036 lines
Diff to previous (colored)

from Changes since 3.6.9:

2014-02-11 - Release

SQLite version fixes a bug present in versions 3.8.1, 3.8.2 and 3.8.3 that can cause queries to omit valid out rows. Upgrading from those versions is recommended.

The problem only comes up if SQLite is compiled with either the SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4 compile-time options. In that case, if a query has a WHERE clause that contains expressions like this:

WHERE (expr1 OR expr2 OR ... OR exprN) AND column IS NOT NULL
Where all of expr1 through exprN are suitable for use by indexes, then during query planning SQLite might mistakenly converted the "column IS NOT NULL" term into "column>NULL". But the latter term is never true, and so the query would return no rows.
The trouble ticket for this bug is [4c86b126f2]. It is recommended that all users upgrade to avoid this problem.

2014-02-03 - Release 3.8.3

SQLite version 3.8.3 is a regularly scheduled maintenance release. Upgrading from the previous release is optional.

The most visible change in version 3.8.3 is the addition of support for common table expressions. It is now possible to write a single SELECT statement that will query a tree or graph, using either a depth-first or a breadth-first search. A single SQLite query will even solve Sudoku puzzles or compute the Mandelbrot set. As part of this change, SQLite now accepts a VALUES clause anyplace that a SELECT statement is valid.

This release also includes many small performance enhancements which should give a small speed boost to legacy applications. And there are other minor enhancements such as the addition of the printf() SQL function. See the change log for details.

2013-12-06 - Release 3.8.2

SQLite version 3.8.2 is a regularly scheduled maintenance release. Upgrading from the previous release is optional.

Version 3.8.2 adds support for WITHOUT ROWID tables. This is a significant extension to SQLite. Database files that contain WITHOUT ROWID tables are not readable or writable by prior versions of SQLite, however databases that do not use WITHOUT ROWID tables are fully backwards and forwards compatible.

The 3.8.2 release contains a potentially incompatible change. In all prior versions of SQLite, a cast from a very large positive floating point number into an integer resulted in the most negative integer. In other words, CAST(+99.9e99 to INT) would yield -9223372036854775808. This behavior came about because it is what x86/x64 hardware does for the equivalent cast in the C language. But the behavior is bizarre. And so it has been changed effective with this release so that a cast from a floating point number into an integer returns the integer between the floating point value and zero that is closest to the floating point value. Hence, CAST(+99.9e99 to INT) now returns +9223372036854775807. Since routines like sqlite3_column_int64() do an implicit cast if the value being accessed is really a floating point number, they are also affected by this change.

Besides the two changes mentioned above, the 3.8.2 release also includes a number of performance enhancements. The skip-scan optimization is now available for databases that have been processed by ANALYZE. Constant SQL functions are now factored out of inner loops, which can result in a significant speedup for queries that contain WHERE clause terms like "date>datetime('now','-2 days')". And various high-runner internal routines have been refactored for reduced CPU load.

2013-10-17 - Release 3.8.1

SQLite version 3.8.1 is a regularly scheduled maintenance release. Upgrading from the previous release is optional, though you should upgrade if you are using partial indices as there was a bug related to partial indices in the previous release that could result in an incorrect answer for count(*) queries.

The next generation query planner that was premiered in the previous release continues to work well. The new query planner has been tweaked slightly in the current release to help it make better decisions in some cases, but is largely unchanged. Two new SQL functions, likelihood() and unlikely(), have been added to allow developers to give hints to the query planner without forcing the query planner into a particular decision.

Version 3.8.1 is the first SQLite release to take into account the estimated size of table and index rows when choosing a query plan. Row size estimates are based on the declared datatypes of columns. For example, a column of type VARCHAR(1000) is assumed to use much more space than a column of type INT. The datatype-based row size estimate can be overridden by appending a term of the form "sz=NNN" (where NNN is the average row size in bytes) to the end of the sqlite_stat1.stat record for a table or index. Currently, row sizes are only used to help the query planner choose between a table or one of its indices when doing a table scan or a count(*) operation, though future releases are likely to use the estimated row size in other contexts as well. The new PRAGMA stats statement can be used to view row size estimates.

Version 3.8.1 adds the SQLITE_ENABLE_STAT4 compile-time option. STAT4 is very similar to STAT3 in that it uses samples from indices to try to guess how many rows of the index will be satisfy by WHERE clause constraints. The difference is that STAT4 samples all columns of the index whereas the older STAT3 only sampled the left-most column. Users of STAT3 are encouraged to upgrade to STAT4. Application developers should use STAT3 and STAT4 with caution since both options, by design, violate the query planner stability guarantee, making it more difficult to ensure uniform performance is widely-deployed and mass-produced embedded applications.

2013-09-03 - Release

SQLite version contains a one-line fix to a bug in the new optimization that tries to omit unused LEFT JOINs from a query.

2013-08-29 - Release

SQLite version fixes some obscure bugs that were uncovered by users in the 3.8.0 release. Changes from 3.8.0 are minimal.

2013-08-26 - Release 3.8.0

Do not fear the zero!
SQLite version 3.8.0 might easily have been called "3.7.18" instead. However, this release features the cutover of the next generation query planner or NGQP, and there is a small chance of breaking legacy programs that rely on undefined behavior in previous SQLite releases, and so the minor version number was incremented for that reason. But the risks are low and there is a query planner checklist is available to application developers to aid in avoiding problems.

SQLite version 3.8.0 is actually one of the most heavily tested SQLite releases ever. Thousands and thousands of beta copies have be downloaded, and presumably tested, and there have been no problem reports.

In addition to the next generation query planner, the 3.8.0 release adds support for partial indices, as well as several other new features. See the change log for further detail.

2013-05-20 - Release 3.7.17

SQLite version 3.7.17 is a regularly schedule maintenance release. Visit the change log for a full explanation of the changes in this release.
There are many bug fixes in version 3.7.17. But this does not indicate that 3.7.16 was a problematic release. All of the bugs in 3.7.17 are obscure and are unlikely to impact any particular application. And most of the bugs that are fixed in 3.7.17 predate 3.7.16 and have been in the code for years without ever before being noticed. Nevertheless, due to the large number of fixes, all users are encouraged to upgrade when possible.

2013-04-12 - Release

SQLite version fixes a long-standing flaw in the Windows OS interface that can result in database corruption under a rare race condition. See for a full description of the problem.
As far as we know, this bug has never been seen in the wild. The problem was discovered by the SQLite developers while writing stress tests for a separate component of SQLite. Those stress tests have not yet found any problems with the component they were intended to verify, but they did find the bug which is the subject of this patch release.

Other than updates to version numbers, the only difference between this release and is a two-character change in a single identifier, which is contained in the windows-specific OS interface logic. There are no changes in this release (other than version numbers) for platforms other than Windows.

2013-03-29 - Release

SQLite version is a bug fix release that fixes a few problems that were present in the previous releases.
The primary motivation for version is to fix a bug in the query optimizer that was introduced as part of version 3.7.15. The query optimizer was being a little overzealous in optimizing out some ORDER BY clauses, which resulted in sorting being omitted on occasions where sorting is required to get the correct answer. See ticket a179fe7465 for details.

In addition to the ORDER BY fix, several other patches to fix obscure (and mostly harmless) bugs and to fix spelling errors in source code comments are also included in this release.

2013-03-18 - Release 3.7.16

SQLite version 3.7.16 is a regularly scheduled release of SQLite. This release contains several language enhancements and improvements to the query optimizer. A list of the major enhancements and optimizations can be see on the change log.
There was one important bug fix (see Ticket fc7bd6358f) that addresses an incorrect query result that could have occurred in a three-way join where the join constraints compared INTEGER columns to TEXT columns. This issue had been in the code for time out of mind and had never before been reported, so we surmise that it is very obscure. Nevertheless, all users are advised to upgrade to avoid any future problems associated with this issue.

2013-01-09 - Release

SQLite version is a patch release that fixes a single bug that was introduced in version version 3.7.15. The fix is a 4-character edit to a single line of code. Other than this 4-character change and the update of the version number, nothing has changed from version

2012-12-19 - Release

SQLite version is a patch release that fixes a single bug that was introduced in version version 3.7.15. The fix involved changing two lines of code and adding a single assert(). This release also includes some new test cases to prevent a regression of the bug, and the version number is increased, of course. But otherwise, nothing has changed from version 3.7.15.
2012-12-12 - Release 3.7.15

SQLite version 3.7.15 is a regularly schedule release of SQLite. This release contains several improvements to the query planner and optimizer and one important bug fix. This is the first release to officially support Windows 8 Phone.
The important bug fix is a problem that can lead to segfaults when using shared cache mode on a schema that contains a COLLATE operator within a CHECK constraint or within a view. Collating functions are associated with individual database connections. But a pointer to the collating function was also being cached within expressions. If an expression was part of the schema and contained a cached collating function, it would point to the collating function in the database connection that originally parsed the schema. If that database connection closed while other database connections using the same shared cache continued to operate, they other database connections would try to use the deallocated collating function in the database connection that closed. The fix in version 3.7.15 was to not cache collating function pointers in the expression structure but instead look them up each time a new statement is prepared.

This release also contains some important enhancements to the query planner which should (we hope) make some queries run faster. The enhancements include:

When doing a full-table scan, try to use an index instead of the original table, under the theory that indices contain less information and are thus smaller and hence require less disk I/O to scan.

Enhance the IN operator to allow it to make use of indices that have numeric affinity.

Do a better job of recognizing when an ORDER BY clause can be implemented using indices - especially in cases where the ORDER BY clause contains terms from two or more tables in a join.

2012-10-04 - Release

SQLite version is a patch release. Changes from the baseline version 3.7.14 are minimal and are restricted to fixing three bugs.
One of the fixed bugs is a long-standing issue with the TCL interface. Another is an external compiler bug that SQLite merely works around and that only comes up if you are using the VisualStudio-2012 compiler to generate WinRT applications on ARM with optimizations enabled. The third problem is an SQLite core bug, introduced in version 3.7.14, that can cause a segfault if a query contains a LEFT JOIN that contains an OR in the ON clause.

2012-09-03 - Release 3.7.14

SQLite version 3.7.14 is a regularly scheduled maintenance release of SQLite. The previous release continues to work well. Upgrading is optional.
Version 3.7.14 drops native support for OS/2. We are not aware of any active projects that were using SQLite on OS/2 and since the SQLite developers had no way of testing on OS/2 it seemed like it was time to simply remove the OS/2 code from the SQLite tree. If there are OS/2 projects out there that still need SQLite support, they can continue to maintain their own private VFS which can be linked to SQLite at start-time using the sqlite3_vfs_register() interface.

The sqlite3_close_v2() interface has been added. The sqlite3_close_v2() interface differs from sqlite3_close() in that it is designed to work better for host language that use a garbage collector. With the older sqlite3_close() interface, the associated prepared statements and sqlite3_backup objects must be destroyed before the database connection. With the newer sqlite3_close_v2() interface, the objects can be destroyed in any order.

This release also includes performance improvements to the sort algorithm that is used to implement ORDER BY and CREATE INDEX. And the query planner has been enhanced to better use covering indices on queries that use OR terms in the WHERE clause.

2012-06-11 - Release 3.7.13

SQLite version 3.7.13 adds support for WinRT and metro style applications for Microsoft Windows 8. The 3.7.13 release is coming sooner than is usual after the previous release in order to get this new capability into the hands of developers. To use SQLite in a metro style application, compile with the -DSQLITE_OS_WINRT flag. Because of the increased application security and safety requirements of WinRT, all database filenames should be full pathnames. Note that SQLite is not capable of accessing databases outside the installation directory and application data directory. This restriction is another security and safety feature of WinRT. Apart from these restrictions, SQLite should work exactly the same on WinRT as it does on every other system.
Also in this release: when a database is opened using URI filenames and the mode=memory query parameter then the database is an in-memory database, just as if it had been named ":memory:". But, if shared cache mode is enabled, then all other database connections that specify the same URI filename will connect to the same in-memory database. This allows two or more database connections (in the same process) to share the same in-memory database.

This release also includes some corner-case performance optimizations that are obscure yet significant to an important subset of SQLite users. Getting these performance optimizations into circulation quickly is yet another reason for making this release so soon following the previous.

The next release of SQLite is scheduled to occur after the usual 2 or 3 month interval.

2012-05-22 - Patch Release

SQLite version is a patch release for version 3.7.12 that fixes a bug that was introduced in version 3.7.12 and that can cause a segfault for certain obscure nested aggregate queries. There are very few changes in, and upgrading is only needed for applications that do nested aggregate queries.
2012-05-14 - Version 3.7.12

SQLite version 3.7.12 is a regularly scheduled maintenance release. This release contains several new optimizations and bug fixes and upgrading is recommended. See the change summary for details.
2012-03-20 - Version 3.7.11

SQLite version 3.7.11 is a regularly scheduled maintenance release which was rushed out early due to a bug in the query optimizer introduced in the previous release. The bug is obscure - it changes a LEFT JOIN into an INNER JOIN in some cases when there is a 3-way join and OR terms in the WHERE clause. But it was considered serious enough to rush out a fix. Apart from this one problem, SQLite version 3.7.10 has not given any trouble. Upgrading to version 3.7.11 from versions, 3.7.7,, 3.7.8, or 3.7.9 is optional. Upgrading from other releases, including the previous release 3.7.10, is recommended.
Other enhancements found in this release are enumerated in the change log.

2012-01-16 - Version 3.7.10

SQLite version 3.7.10 is a regularly scheduled maintenance release. Upgrading from version, 3.7.7,, 3.7.8, or 3.7.9 is optional. Upgrading from other releases is recommended.
The SQLITE_CONFIG_PCACHE mechanism has been replaced with SQLITE_CONFIG_PCACHE2. If you do not know what this mechanism is (it is an extreme corner-case and is seldom used) then this change will not effect you in the least.

The default schema format number for new database files has changed from 1 to 4. SQLite has been able to generate and read database files using schema format 4 for six years. But up unto now, the default schema format has been 1 so that older versions of SQLite could read and write databases generated by newer versions of SQLite. But those older versions of SQLite have become so scarce now that it seems reasonable to make the new format the default.

SQLite is changing some of the assumptions it makes above the behavior of disk drives and flash memory devices during a sudden power loss. This change is completely transparent to applications. Read about the powersafe overwrite property for additional information.

Lots of new interfaces have been added in this release:

PRAGMA shrink_memory
The PRAGMA cache_size statement has been enhanced. Formerly, you would use this statement to tell SQLite how many pages of the database files it should hold in its cache at once. The total memory requirement would depend on the database page size. Now, if you give PRAGMA cache_size a negative value -N, it will allocate roughly N kibibytes of memory to cache, divided up according to page size. This enhancement allows programs to more easily control their memory usage.

There have been several obscure bug fixes. One noteworthy bug, ticket ff5be73dee, could in theory result in a corrupt database file if a power loss occurred at just the wrong moment on an unusually cantankerous disk drive. But that is mostly a theoretical concern and is very unlikely to happen in practice. The bug was found during laboratory testing and has never been observed to occur in the wild.

2011-11-01 - Version 3.7.9

SQLite version 3.7.9 is a regularly scheduled maintenance release. Upgrading from version, 3.7.7,, and 3.7.8 is optional. Upgrading from other versions is recommended.
The SQLITE_ENABLE_STAT2 compile-time option is now a no-op. The enhanced query-planner functionality formerly available using SQLITE_ENABLE_STAT2 is now available through SQLITE_ENABLE_STAT3. The enhanced query planning is still disabled by default. However, future releases of SQLite might convert STAT3 from an enable-option to a disable-option so that it is available by default and is only omitted upon request.

The FTS4 full-text search engine has been enhanced such that tokens in the search string that begin with "^" must be the first token in their respective columns in order to match. Formerly, "^" characters in the search string were simply ignored. Hence, if a legacy application was including "^" characters in FTS4 search strings, thinking that they would always be ignored, then those legacy applications might break with this update. The fix is simply remove the "^" characters from the search string.

See the change summary for additional changes associated with this release.

2011-September-19 - Version 3.7.8

SQLite version 3.7.8 is a quarterly maintenance release. Upgrading from versions, 3.7.7, or is optional. Upgrading from other versions is recommended.
This release features a new "external merge sort" algorithm used to implement ORDER BY and GROUP BY and also to presort the content of an index for CREATE INDEX. The new algorithm does approximately the same number of comparisons and I/Os as before, but the I/Os are much more sequential and so runtimes are greatly reduced when the size of the set being sorted is larger than the filesystem cache. The performance improvement can be dramatic - orders of magnitude faster for large CREATE INDEX commands. On the other hand, the code is slightly slower (1% or 2%) for a small CREATE INDEX. Since CREATE INDEX is not an operation that commonly occurs on a speed-critical path, we feel that this tradeoff is a good one. The slight slowdown for small CREATE INDEX statements might be recovered in a future release. ORDER BY and GROUP BY operations should now be faster for all cases, large and small.

The query planner has been enhanced to do a better job of handling the DISTINCT keyword on SELECT statements.

There has been a lot of work on the default VFSes. The unix VFS has been enhanced to include more overrideable system calls - a feature requested by Chromium to make it easier to build SQLite into a sandbox. The windows VFS has been enhanced to be more resistant to interference from anti-virus software.

Every version of SQLite is better tested than the previous, and 3.7.8 is no exception to this rule. Version 3.7.8 has been used internally by the SQLite team for mission critical functions and has performed flawlessly. And, of course, it passes our rigorous testing procedures with no problems detected. Version 3.7.8 is recommended for all new development.

2011-06-28 - Version

SQLite version adds a one-line bug fix to 3.7.7 to fix a problem causing PRAGMA case_sensitive_like statements compiled using the legacy sqlite3_prepare() interface to fail with an SQLITE_SCHEMA error. Because sqlite3_exec() uses sqlite3_prepare() internally, the problem also affects sqlite3_exec().
Upgrading from 3.7.7 is only required for applications that use "PRAGMA case_sensitive_like" and the sqlite3_prepare() (or sqlite3_exec()) interface.

2011-06-24 - Version 3.7.7

SQLite version 3.7.7 is a regularly scheduled bi-monthly maintenance release. Upgrading from version is optional. Upgrading from all prior releases is recommended.
This release adds support for naming database files using URI filenames. URI filenames are disabled by default (for backwards compatibility) but applications are encouraged to enable them since incompatibilities are likely to be exceedingly rare and the feature is useful. See the URI filename documentation for details.

Most of the other enhancements in this release involve virtual tables. The virtual table interface has been enhanced to support SAVEPOINT and ON CONFLICT clause processing, and the built-in RTREE and FTS3/FTS4 have been augmented to take advantage of the new capability. This means, for example, that it is now possible to use the REPLACE command on FTS3/FTS4 and RTREE tables.

The FTS4 full-text index extension has been enhanced to support the FTS4 prefix option and the FTS4 order option. These two enhancements are provided in support of search-as-you-type interfaces where search results begin to appear after the first keystroke in the "search" box and are refined with each subsequent keystroke. The way this is done is to do a separate full-text search after each key stroke, and add the "*" wildcard at the end of the word currently being typed. So, for example, if the text typed so far is "fast da" and the next character typed is "t", then the application does a full-text search of the pattern "fast dat*" and displays the results. Such capability has always existed. What is new is that the FTS4 prefix option allows the search to be very fast (a matter of milliseconds) even for difficult cases such as "t*" or "th*".

There has been a fair amount of work done on the FTS4 module for this release. But the core SQLite code has changed little and the previous release has not given any problems, so we expect this to be a very stable release.

2011-05-19 - Version

SQLite version is a patch release that fixes a single bug associated with WAL mode. The bug has been in SQLite ever since WAL was added, but the problem is very obscure and so nobody has noticed before now. Nevertheless, all users are encouraged to upgrade to version or later.
The bug is this: If the cache_size is set very small (less than 10) and SQLite comes under memory pressure and if a multi-statement transaction is started in which the last statement prior to COMMIT is a SELECT statement and if a checkpoint occurs right after the transaction commit, then it might happen that the transaction will be silently rolled back instead of being committed.

The default setting for cache_size is 2000. So in most situations, this bug will never appear. But sometimes programmers set cache_size to very small values on gadgets and other low-memory devices in order to save memory space. Such applications are vulnerable. Note that this bug does not cause database corruption. It is as if ROLLBACK were being run instead of COMMIT in some cases.

Bug Details

Transactions commit in WAL mode by adding a record onto the end of the WAL (the write-ahead log) that contains a "commit" flag. So to commit a transaction, SQLite takes all the pages that have changed during that transaction, appends them to the WAL, and sets the commit flag on the last page. Now, if SQLite comes under memory pressure, it might try to free up memory space by writing changed pages to the WAL prior to the commit. We call this "spilling" the cache to WAL. There is nothing wrong with spilling cache to WAL. But if the memory pressure is severe, it might be that by the time COMMIT is run, all changed pages for the transaction have already been spilled to WAL and there are no pages left to be written to WAL. And with no unwritten pages, there was nothing to put the commit flag on. And without a commit flag, the transaction would end up being rolled back.

The fix to this problem was that if all changed pages has already been written to the WAL when the commit was started, then page 1 of the database will be written to the WAL again, so that there will always be a page available on which to set the commit flag.

2011-04-17 - Version

SQLite version adds a one-line bug fix to that enables pthreads to work correctly on NetBSD. The problem was a faulty function signature for the open system call. The problem does not appear to have any adverse impact on any system other than NetBSD.
Upgrading from version is only needed on NetBSD.

2011-04-13 - Version

SQLite version fixes a single bug in 3.7.6 that can cause a segfault if SQLITE_FCNTL_SIZE_HINT is used on a unix build that has SQLITE_ENABLE_LOCKING_MODE set to 0 and is compiled with HAVE_POSIX_FALLOCATE.
Upgrading from 3.7.6 is only needed for users effected by the configuration-specific bug described above. There are no other changes to the code.

2011-04-12 - Version 3.7.6

SQLite version 3.7.6 is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from version 3.7.5 is optional. Upgrading releases prior to 3.7.5 is recommended.
2011-02-01 - Version 3.7.5

SQLite version 3.7.5 is a regularly scheduled bi-monthly maintenance release of SQLite. Due to the discovery and fix of an obscure bug that could cause database corruption, upgrading from all prior releases of SQLite is recommended. This bug was found during code review and has not been observed in the wild.
This release adds new opcodes for the sqlite3_db_status() interface that allow more precise measurement of how the lookaside memory allocator is performing, which can be useful for tuning in applications with very tight memory constraints.

The sqlite3_vsnprintf() interface was added. This routine is simply a varargs version of the long-standing sqlite3_snprintf() interface.

The output from sqlite3_trace() interface has been enhanced to work better (and faster) in systems that use recursive extensions such as FTS3 or RTREE.

Testing with Valgrind shows that this release of SQLite is about 1% or 2% faster than the previous release for most operations.

A fork of the popular ADO.NET adaptor for SQLite known as System.Data.SQLite is now available on The originator of System.Data.SQLite, Robert Simpson, is aware of this fork, has expressed his approval, and has commit privileges on the new Fossil repository. The SQLite development team intends to maintain System.Data.SQLite moving forward.

2010-12-08 - Version 3.7.4

SQLite version 3.7.4 is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from version 3.7.2 and version 3.7.3 is optional. Upgrading from all other SQLite releases is recommended.
This release features full-text search enhancements. The older FTS3 virtual table is still fully supported, and should also run faster. In addition, the new FTS4 virtual table is added. FTS4 follows the same syntax as FTS3 but holds additional metadata which facilitates some performance improvements and more advanced matchinfo() output. Look for further full-text search enhancements in subsequent releases.

Also in this release, the EXPLAIN QUERY PLAN output has been enhanced and new documentation is provided so that application developers can more easily understand how SQLite is performing their queries.

Thanks to an account from the folks at, OpenBSD has been added to the list of platforms upon which we test SQLite prior to every release. That list of platforms now includes:

Linux x86 & x86_64
MacOS 10.5 & 10.6
MacOS 10.2 PowerPC
WinXP and Win7
Android 2.2
OpenBSD 4.7
The previous release of SQLite (version 3.7.3) has proven to be very robust. The only serious issue discovered was ticket 80ba201079 that describes an incorrect query result that can occur under very unusual circumstances. The ticket description contains details of the problem. Suffice it to say here that the problem is very obscure and is unlikely to effect most applications and so upgrading is optional. The problem is fixed, of course, in this release.

2010-October-08 - Version 3.7.3

SQLite version 3.7.3 is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from version 3.7.2 is optional. Upgrading from all other releases is recommended.
This release adds two new interfaces (really just variations on existing interfaces). The sqlite3_create_function_v2() interface adds a destructor for the application-data pointer. The new sqlite3_soft_heap_limit64() interface allows the soft heap limit to be set to a value greater than 231.

The RTREE extension has been enhanced with the ability to have an application-defined query region. This might be used, for example, to locate all objects within the field of view of a camera.

The 3.7.3 release also includes some performance enhancements, including query planner improvements, documentation updates, and fixes to some very obscure bugs.

2010-August-24 - Version 3.7.2

SQLite version 3.7.2 fixes a long-standing bug that can cause the database free-page list to go corrupt if incremental_vacuum is used multiple times to partially reduce the size of a database file that contains many hundreds of unused database pages. The original bug reports together with links to the patch that fixes it can be seen here.
This bug has been in the code for at least a year and possibly longer. The bug has nothing to do with the versions 3.7.1 or 3.7.0 or any other recent release. The fact that the bug was discovered (and fixed) within hours of the 3.7.1 release is purely a coincidence.

The bug is impossible to hit without using incremental_vacuum and is very difficult to hit even with incremental_vacuum. And the kind of corruption that the bug causes can usually be fixed simply by running VACUUM. Nevertheless, because the bug can result in database corruption, it is recommended that all SQLite users upgrade to version 3.7.2 or later.

2010-August-23 - Version 3.7.1

SQLite version 3.7.1 is a stabilization release for the 3.7.x series. Other than the filesize-in-header bug that was fixed in version, no major problems have been seen in 3.7.0. Some minor corner-case performance regressions have been fixed. A typo in the OS/2 interface has been repaired.
A biggest part of the 3.7.1 release is a cleanup and refactoring of the pager module within SQLite. This refactoring should have no application-visible effects. The purpose was to reorganize the code in ways that make it easier to prove correctness.

The 3.7.1 release adds new experimental methods for obtained more detailed memory usage information and for controlling database file fragmentation. And the query planner now does a better job of optimizing the LIKE and GLOB operators.

This release increases the maximum size of database pages from 32KiB to 64KiB. A database with 64KiB pages will not be readable or writable by older versions of SQLite. Note that further increases in page size are not feasible since the file format uses 16-bit offsets to structures within each page.

2010-August-04 - Version

SQLite version is a patch release to fix a bug in the new filesize-in-header feature of the SQLite file format that could cause database corruption if the same database file is written alternately with version 3.7.0 and version or earlier. A performance regression was also fixed in this release.
2010-07-22 - Version 3.7.0

SQLite version 3.7.0 is a major release of SQLite that features a new transaction control mechanism using a write-ahead log or WAL. The traditional rollback-journal is still used as the default so there should be no visible change for legacy programs. But newer programs can take advantage of improved performance and concurrency by enabling the WAL journaling mode.
SQLite version 3.7.0 also contains some query planner enhancements and a few obscure bug fixes, but the only really big change is the addition of WAL mode.

2010-03-30 - Version

SQLite version is a patch release to fix a bug in the offsets() function of FTS3 at the request of the Mozilla.
2010-03-09 - Version 3.6.23

SQLite version 3.6.23 is a regular bimonthly release of SQLite. Upgrading from the prior release is purely optional.
This release contains new pragmas: the secure_delete pragma, and the compile_options pragma. There are a new SQL functions: sqlite_compileoption_used() and sqlite_compileoption_get(). New C/C++ interfaces: sqlite3_compileoption_used(), sqlite3_compileoption_get(), SQLITE_CONFIG_LOG, and sqlite3_log().

This release also includes several minor bug fixes and performance improvements. Support for SQLITE_OMIT_FLOATING_POINT is enhanced. There are on-going improvements to FTS3.

The ".genfkey" command in the Command Line Interface has been removed. SQLite has supported standard SQL foreign key constraints since version 3.6.19 and so the ".genfkey" command was seen as an anachronism.

2010-01-06 - Version 3.6.22

SQLite version 3.6.22 is a bug-fix release. Two bugs have been fixed that might cause incorrect query results.
Ticket 31338dca7e describes a problem with queries that have a WHERE clause of the form (x AND y) OR z where x and z come from one table of a join and y comes from a different table.
Ticket eb5548a849 describes a problem where the use of the CAST operator in the WHERE clause can lead to incorrect results if the column being cast to a new datatype is also used in the same WHERE clause without being cast.
Both bugs are obscure, but because they could arise in an application after deployment, it is recommended that all applications upgrade SQLite to version 3.6.22.
This release also includes other minor bug fixes and performance enhancements, especially in the FTS3 extension.

2009-12-07 - Version 3.6.21

SQLite version 3.6.21 focuses on performance optimization. For a certain set of traces, this version uses 12% fewer CPU instructions than the previous release (as measured by Valgrind). In addition, the FTS3 extension has been through an extensive cleanup and rework and the sqlite3_trace() interface has been modified to insert bound parameter values into its output.
2009-11-04 - Version 3.6.20

SQLite version 3.6.20 is a general maintenance release. The query planner has been enhanced to work better with bound parameters in LIKE and GLOB operators and in range constraints and various minor bugs have been fixed. Upgrading from 3.6.19 is optional.
2009-10-14 - Version 3.6.19

SQLite version 3.6.19 adds native support for foreign key constraints, including deferred constraints and cascading deletes. Enforcement of foreign keys is disabled by default for backwards compatibility and must be turned on using the foreign_keys pragma.
Version 3.6.19 also adds support for the IS and IS NOT operators. Formerly, SQLite (as most other SQL database engines) supported IS NULL and IS NOT NULL. The IS and IS NOT operators are generalizations that allow the right-hand side to be an arbitrary expression. IS and IS NOT work the same as == (equals) and != (not equals) except that with IS and IS NOT the NULL values compare equal to one another.

2009-09-11 - Version 3.6.18

Beginning with this release, the SQLite source code is tracked and managed using the Fossil distributed configuration management system. SQLite was previously versioned using CVS. The entire CVS history has been imported into Fossil. The older CVS repository remains on the website but is read-only.
There are two major enhancements in SQLite version 3.6.18. The first is a series or refinements to the query planner that help SQLite to choose better plans for joins where in the past it was selecting suboptimal query plans. The SQLITE_ENABLE_STAT2 compile-time option has been added to cause SQLite to collect histogram data on indices when the ANALYZE command is run. The use of histograms improve the query planning performance even more.

The second major enhancement is that SQLite now support recursive triggers. The older non-recursive behavior of triggers is still the default behavior. Recursive triggers are activated using the recursive_triggers pragma. In addition to allowing triggers to call themselves (either directly or indirectly) the new capability also fires DELETE triggers on rows that are removed from a table as a result of REPLACE conflict resolution processing.

Non-recursive triggers are still the default behavior since this is least likely to cause problems for existing applications. However, we anticipate that triggers will become recursive by default beginning with release 3.7.0. At that point, applications that want to continue using the older non-recursive trigger behavior will need to use the recursive_triggers pragma to disable recursive triggers.

This version of SQLite also contains bug fixes, though none of the bugs are serious and all are obscure, so upgrading is optional.

The SQLite core continues to have 100% branch test coverage and so despite the many changes in this release, the developers believe that this version of SQLite is stable and ready for production use.

2009-08-10 - Version 3.6.17

This is a monthly maintenance release with a focus of bug fixes, performance improvements, and increased test coverage. This is the first release of SQLite since 100% branch test coverage was achieved on the SQLite core.
In addition, a new interface sqlite3_strnicmp() is provided for the convenience of extension writers.

None of the bugs fixed in this release are serious. All bugs are obscure. Upgrading is optional.

2009-07-25 - 100% Branch Test Coverage

A subset of the TH3 test suite was measured by gcov to provide 100% branch test coverage over the SQLite core (exclusive of the VFS backend and of extensions such as FTS3 and RTREE) when compiled for SuSE 10.1 Linux on x86. The SQLite developers pledge to maintain branch test coverage at 100% in all future releases. Ongoing work will strive for 100% branch test coverage on the operating-system backends and extensions as well.
2009-06-27 - Version 3.6.16

SQLite version 3.6.16 is another general maintenance release containing performance and robustness enhancements. A single notable bug was fixed (ticket #3929). This bug cause cause INSERT or UPDATE statements to fail on indexed tables that have AFTER triggers that modify the same table and index.
2009-06-15 - Version 3.6.15

SQLite version 3.6.15 is a general maintenance release containing performance and robustness enhancements and fixes for various obscure bugs.
2009-05-25 - Version

SQLite version fixes an obscure bug in the code generator (ticket #3879) section of SQLite which can potentially cause incorrect query results. The changes from the prior release consist of only this one bug fix, check-in [6676] and a change to the version number text.
The bug was introduced in version 3.6.14. It is recommended that users of version 3.6.14 and upgrade to this release. Applications are unlikely to hit this bug, but since it is difficult to predict which applications might hit it and which might not, we recommend that all users of 3.6.14 and upgrade to this release.

2009-05-19 - Version

SQLite version is a patch release to version 3.6.14 with minimal changes that fixes three bugs. Upgrading is only necessary for users who are impacted by one or more of those bugs.
2009-05-07 - Version 3.6.14

SQLite version 3.6.14 provides new performance enhancements in the btree and pager layers and in the query optimizer. Certain workloads can be as much as twice as fast as the previous release, though 10% faster is a more typical result.
Queries against virtual tables that contain OR and IN operators in the WHERE clause are now able to use indexing.

A new optional asynchronous I/O backend is available for unix and windows. The asynchronous backend gives the illusion of faster response time by pushing slow write operations into a background thread. The tradeoff for faster response time is that more memory is required (to hold the content of the pending writes) and if a power failure or program crash occurs, some transactions that appeared to have committed might end up being rolled back upon restart.

This release also contains many minor bug fixes, documentation enhancements, new test cases, and cleanups and simplifications to the source code.

There is no compelling reason to upgrade from versions 3.6.12 or 3.6.13 if those prior versions are working. Though many users may benefit from the improved performance.

Revision 1.8 / (download) - annotate - [select for diffs], Thu Feb 14 21:07:25 2013 UTC (11 years ago) by martin
Branch: MAIN
CVS Tags: riastradh-drm2-base2, riastradh-drm2-base1, riastradh-drm2-base, riastradh-drm2, agc-symver-base, agc-symver
Changes since 1.7: +4 -4 lines
Diff to previous 1.7 (colored)

Backout previous

Revision 1.7 / (download) - annotate - [select for diffs], Thu Feb 14 17:12:23 2013 UTC (11 years ago) by martin
Branch: MAIN
Changes since 1.6: +5 -5 lines
Diff to previous 1.6 (colored)

When converting long double values to decimal, convert to int via a call
to floor(), so the conversion does not depend on current rounding mode.
Fixes PR port-sparc64/47535.

Revision / (download) - annotate - [select for diffs], Tue Apr 17 00:04:51 2012 UTC (11 years, 10 months ago) by yamt
Branch: yamt-pagecache
CVS Tags: yamt-pagecache-tag8
Changes since +5551 -3320 lines
Diff to previous (colored) to branchpoint (colored)

sync with head

Revision 1.6 / (download) - annotate - [select for diffs], Mon Feb 6 17:24:49 2012 UTC (12 years ago) by matt
Branch: MAIN
CVS Tags: yamt-pagecache-base8, yamt-pagecache-base7, yamt-pagecache-base6, yamt-pagecache-base5, yamt-pagecache-base4, netbsd-6-base, netbsd-6-1-RELEASE, netbsd-6-1-RC4, netbsd-6-1-RC3, netbsd-6-1-RC2, netbsd-6-1-RC1, netbsd-6-1-5-RELEASE, netbsd-6-1-4-RELEASE, netbsd-6-1-3-RELEASE, netbsd-6-1-2-RELEASE, netbsd-6-1-1-RELEASE, netbsd-6-1, netbsd-6-0-RELEASE, netbsd-6-0-RC2, netbsd-6-0-RC1, netbsd-6-0-6-RELEASE, netbsd-6-0-5-RELEASE, netbsd-6-0-4-RELEASE, netbsd-6-0-3-RELEASE, netbsd-6-0-2-RELEASE, netbsd-6-0-1-RELEASE, netbsd-6-0, netbsd-6, matt-nb6-plus-nbase, matt-nb6-plus-base, matt-nb6-plus
Branch point for: tls-maxphys
Changes since 1.5: +2 -6 lines
Diff to previous 1.5 (colored)

Back out part of previous commit (no reason to define SQLITE_BIG_DBL
especially for VAX since it uses DBL_MAX from the VAX <float.h>).

Revision 1.5 / (download) - annotate - [select for diffs], Sun Feb 5 17:55:12 2012 UTC (12 years ago) by matt
Branch: MAIN
Changes since 1.4: +10 -3 lines
Diff to previous 1.4 (colored)

Make this compilable by VAX GCC 4.5

Revision 1.4 / (download) - annotate - [select for diffs], Sat Jan 28 23:55:36 2012 UTC (12 years, 1 month ago) by joerg
Branch: MAIN
Changes since 1.3: +5551 -3327 lines
Diff to previous 1.3 (colored)

Merge Sqlite 3.7.10.

Revision / (download) - annotate - [select for diffs] (vendor branch), Sat Jan 28 23:51:03 2012 UTC (12 years, 1 month ago) by joerg
Branch: SQLITE
CVS Tags: sqlite-3-7-10
Changes since +5547 -3319 lines
Diff to previous (colored)

Update to sqlite 3.7.10:
- Default schema format changed to version 4
- Various bugfixes and improvements.

Revision 1.3 / (download) - annotate - [select for diffs], Mon Jan 9 11:20:20 2012 UTC (12 years, 1 month ago) by martin
Branch: MAIN
Changes since 1.2: +8 -4 lines
Diff to previous 1.2 (colored)

When aggregate-allocating an index structure make sure to provide at least
natural alignement for pointers.
This makes firefox 3.6 work again on sparc64.

Revision / (download) - annotate - [select for diffs], Thu Nov 10 14:31:27 2011 UTC (12 years, 3 months ago) by yamt
Branch: yamt-pagecache
Changes since +12 -3 lines
Diff to previous (colored)

sync with head

Revision 1.2 / (download) - annotate - [select for diffs], Wed Nov 2 23:19:48 2011 UTC (12 years, 4 months ago) by christos
Branch: MAIN
CVS Tags: yamt-pagecache-base3, yamt-pagecache-base2
Changes since 1.1: +12 -3 lines
Diff to previous 1.1 (colored)

fix vax floating point overflows.

Revision / (download) - annotate - [select for diffs] (vendor branch), Thu Oct 13 21:38:52 2011 UTC (12 years, 4 months ago) by joerg
Branch: SQLITE
CVS Tags: yamt-pagecache-base, sqlite-3-7-9-pre
Branch point for: yamt-pagecache
Changes since 1.1: +0 -0 lines
Diff to previous 1.1 (colored)

Import pre-release of SQLite 3.6.9 based on 8bf13b036a.

Revision 1.1 / (download) - annotate - [select for diffs], Thu Oct 13 21:38:52 2011 UTC (12 years, 4 months ago) by joerg
Branch: MAIN

Initial revision

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

CVSweb <>