Recent SQLite News

From 63847496f14c813a5d80efd5b7de0f1294ffe1e3 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 13 Apr 2024 16:07:11 +0200 Subject: Adding upstream version 3.45.1. Signed-off-by: Daniel Baumann --- www/news.html | 835 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 835 insertions(+) create mode 100644 www/news.html (limited to 'www/news.html') diff --git a/www/news.html b/www/news.html new file mode 100644 index 0000000..b01454b --- /dev/null +++ b/www/news.html @@ -0,0 +1,835 @@ + + + + + +Recent SQLite News + + + +

+ +

+Small. Fast. Reliable.
Choose any three. +

+ + +

+ +

+ + + +

Recent News

+ +

2024-01-30 - Version 3.45.1

+Version 3.45.1 is a patch against SQLite version 3.45.0. +
+The main focus of this patch release is to restore certain +undocumented legacy behavior in the JSON SQL functions that +the developers were unaware of but which some applications +had come to depend on. This undocumented behavior was "fixed" +in the 3.45.0, resulting in breakage for applications that were +using it. So it has now been restored and documented. +
+Other obscure issues that have come up since the 3.45.0 release, +some related to the release itself and some going back years, +are also fixed. +

2024-01-15 - Version 3.45.0

+Version 3.45.0 is an enhancement release of SQLite. +
+The most impactful change is likely enhancements to +the JSON SQL functions such that they are now able to +store their internal JSON parse trees in the database +as BLOB values. This can significantly increase the +performance of applications that process large JSON +strings as it omits the need to translate JSON text +to and from the internal binary format used by SQLite. +
+A second noteworthy change is that any +application-defined SQL functions that make use of +the sqlite3_result_subtype() interface must now include +the SQLITE_RESULT_SUBTYPE attribute when the function +is registered using sqlite3_create_function() or similar. +Failure to include the SQLITE_RESULT_SUBTYPE attribute on +functions that use sqlite3_result_subtype() might result +in incorrect answers. +
+See the change log +for additional enhancements that are part of the 3.45.0 release. +

2023-11-24 - Version 3.44.2

+The CLI fix in version 3.44.1 introduced a new bug, which is +fixed by patch release 3.44.2. Version 3.44.2 also fixes an +FTS5 problem that was found by a fuzzer just minutes after the +3.44.1 release. +

2023-11-22 - Version 3.44.1

+Version 3.44.1 is a patch release that fixes various obscure +bugs. There is no need to upgrade, unless you are having +problems with a prior release. +

2023-11-01 - Version 3.44.0

+Version 3.44.0 is new enhancement release of SQLite. +
+It has only been 69 days since the previous major +release (3.43.0). The original plan was for version 3.44.0 +to occur at a spacing of approximately 120 days from the +prior release. However, the code accumulated so many important +enhancements that is seemed better to accelerate the release +of 3.44.0, thus getting those enhancements into circulation. +This means that some enhancements that where originally +planned to be in 3.44.0 have been deferred until subsequent +releases. +

2023-10-10 - Version 3.43.2

+Version 3.43.2 is a patch release that fixes a few small inaccuracies in +version 3.43.0 and 3.43.1. +

2023-09-11 - Version 3.43.1

+Version 3.43.1 is a patch release that fixes a few small inaccuracies that were +discovered in the the 3.43.0 and/or 3.42.0 releases after the 3.43.0 release was +published. +

2023-08-24 - Version 3.43.0

+Version 3.43.0 is a routine enhancement release of SQLite. +Key enhancements in this release include added support for +Contentless-Delete FTS5 Indexes, +and performance improvements in JSON processing. +See the change log for +details. +

2023-05-16 - Version 3.42.0

+Version 3.42.0 is a routine enhancement release of SQLite. +Key enhancements in this release are added support for +JSON5 and the FTS5 secure-delete command. See the +change log for a +summary of all enhancements in this release. +

2023-03-22 - Version 3.41.2

+Version 3.41.2 is a patch release that fixes multiple +fuzzer-found problems in prior releases. The worst problems +include reads (not writes) past the end of a buffer. Upgrading +is recommended. +

2023-03-10 - Version 3.41.1

+Version 3.41.1 is a patch release that fixes various obscure +problems found in 3.41.0 and reported by users. Upgrading +is optional. +

2023-02-21 - Version 3.41.0

+Version 3.41.0 is a routine enhancement release. +

2022-12-28 - Version 3.40.1

+Version 3.40.1 is a patch release that fixes some obscure problems +in version 3.40.0. The problems fixed have no impact on most applications. +Upgrading is only necessary if you encounter problems. +
+The two most important fixes are these: +
+
+Fix the safe command-line option on the CLI so that it +correctly disallows functions with side-effects. This is a bug +in the CLI — not a bug in the +SQLite library — and it only affects the --safe command-line +option, making that option less than fully "safe". As the number +of systems that use the --safe command-line option in the CLI is +approximately zero, this is not considered an important bug. However, +a third-party wrote a CVE against it which caused considerable angst +among maintainers, so it seems good to get the fix into circulation +sooner rather than wait on the next major release. +
+The optional memsys5 memory allocator picked up a bug that might +put it into an infinite loop for very large (500MiB) allocations. +Almost all systems use their native memory allocator, not memsys5. +Memsys5 is only used if SQLite is compiled using SQLITE_ENABLE_MEMSYS5 +and then initialized using sqlite3_config(SQLITE_CONFIG_HEAP). +Very, very few systems do this, and so the problem is not considered +to be serious. +
+
+See the branch-3.40 timeline +for a complete listing of changes that have gone into this patch release. +

2022-11-16 - Version 3.40.0

+Version 3.40.0 is a new feature release of SQLite. See the +change log for details. +Key enhancements in this release include: +
+
+Official support for compiling +SQLite to WASM +and running it in a web browser. +
+New and improved recovery extension for extracting +data from corrupted database files. +
+
+This release also includes performance enhancements and +improvements to the query planner. +
+A psychological milestone: The performance benchmark that +the SQLite developers have used for many years has for +the first time dropped below 1 billion CPU cycles +(measured using cachegrind) when run in WAL mode. +This is less than half the number of CPU cycles used as +recently as 8 years ago. (The graph below shows SQLite using +a rollback journal which uses fewer CPU cycles at the expense +of extra I/O. The benchmark passed through the 1 billion cycle +barrier for rollback journals for the previous release.) +
+ +
+

2022-09-29 - Version 3.39.4

+Version 3.39.4 is a security release that addresses a single +long-standing problem in the FTS3 extension. An attacker +who is able to execute arbitrary SQL statements and who can create +a corrupt database that is 2GB or larger in size might be able to trick +FTS3 into overflowing an integer used to size a memory allocation, +causing the allocation to be too small and ultimately resulting in +a buffer overrun. The release also includes fixes for other +obscure weaknesses, as described in the release notes. +

2022-09-05 - Version 3.39.3

+Version 3.39.3 is a patch release that fixes a few obscure problems +in the 3.39.0 release. See the release notes for details. +

2022-07-21 - Version 3.39.2

+Version 3.39.2 is a security release that addresses multiple long-standing +issues in SQLite. The most severe problem is identified by CVE-2022-35737. +That issue is associated with the auxiliary C-language APIs +of SQLite and cannot be reached using SQL or database inputs, and hence is +unlikely to affect your application. Nevertheless, upgrading is recommended. +The other issues are comparatively minor. +This release also fixes a performance regression that appeared in version +3.39.0 that might affect some multi-way joins that use LEFT JOIN. +

2022-07-13 - Version 3.39.1

+Version 3.39.1 is a patch release that fixes a few minor problem in version +3.39.0. Upgrading is optional. +

2022-06-25 - Version 3.39.0

+Version 3.39.0 is regular maintenance release of SQLite. The key enhancement +in this release is added support for RIGHT and FULL JOIN. There are other +language and performance enhancements as well — see the +release notes for details. +

2022-05-06 - Version 3.38.5

+The 3.38.4 patch release included a minor change to the CLI source code +that did not work. The release manager only ran a subset of the normal +release tests, and hence did not catch the problem. As a result, the CLI +will segfault when using columnar output modes in version 3.38.4. This +blunder did not affect the core SQLite library. It only affected the CLI. +
+Take-away lesson: Always run all of your tests prior to +a release - even a trival patch release. Always. +
+The 3.38.5 patch release fixes the 3.38.4 blunder. +

2022-05-04 - Version 3.38.4

+Another user-discovered problem in the new Bloom filter optimization +is fixed in this patch release. Without the fix, it is possible for +a multi-way join that uses a Bloom filters for two or more tables in +the join to enter an infinite loop if the key constraint on one of those +tables contains a NULL value. +

2022-04-27 - Version 3.38.3

+Version 3.38.3 fixes a bug in the automatic-index and Bloom filter +construction logic that might cause SQLite to be overly aggressive +in the use of ON clause constraints, resulting in an incorrect +automatic-index or Bloom filter that excludes some valid rows from +output. The bug was introduced in version 3.38.0. Other minor +changes were tossed in to complete the patch. +

2022-03-26 - Version 3.38.2

+Version 3.38.2 fixes another bug in the new Bloom filter +optimization that might cause incorrect answers for a +LEFT JOIN that has an IS NULL constraint on the right-hand +table. +

2022-03-12 - Version 3.38.1

+Version 3.38.1 fixes a pair of bugs in the Bloom filter +optimization that was introduced in version 3.38.0. These +bugs might cause incorrect answers for some obscure queries. +Various other minor problems and documentation typos were +fixed at the same time. +

2022-02-22 - Version 3.38.0

+Version 3.38.0 is a routine maintenance release of +SQLite. There are various minor enhancements and +about a 0.5% reduction in the number of CPU cycles +used. See the +release notes for +more detail. +

2022-01-06 - Version 3.37.2

+Version 3.37.2 fixes a +database corruption bug. You are +encouraged to upgrade, especially if you are using SAVEPOINT.
+ +
The problem first appeared in version 3.35.0 (2021-03-12) and +affects all subsequent releases through 3.37.1. +If temporary files are store in memory (which is not the default +behavior, but is sometimes selected by applications using either +-DSQLITE_TEMP_STORE or PRAGMA temp_store) and +if a SAVEPOINT is rolled back and then subsequent changes +within the same transaction are committed, the database file might +(with low but non-zero probability) go corrupt. +

2021-12-30 - Version 3.37.1

+Version 3.37.1 fixes a bug in the UPSERT logic, introduced by +the UPSERT enhancements of version 3.35.0, that can cause +incorrect byte-code to be generated in some cases, resulting +in an infinite loop in the byte code, or a NULL-pointer dereference. +This patch release also fixes some other minor problems with +assert() statements and in the CLI. +

2021-11-27 - Version 3.37.0

+Version 3.37.0 is a routine maintenance release of SQLite. +The biggest new feature in this release is support for +STRICT tables. Other enhancements are described in +the release notes. +

2021-06-18 - Version 3.36.0

+Version 3.36.0 is a routine maintenance release of SQLite. +There are no new major features, only incremental improvements +to existing features and small performance improvements. +

2021-04-19 - Patch release 3.35.5

+The new ALTER TABLE DROP COLUMN capability that was added +in the 3.35.0 release contained a bug that might cause the +table content to go corrupt when the table was rewritten +to remove the dropped column. Fixed by this patch. +

2021-04-02 - Patch release 3.35.4

+Version 3.35.4 is yet another patch release to fix +obscure problems in features associated with the 3.35.0. +

2021-03-26 - Patch release 3.35.3

+Version 3.35.3 contains patches for a handful of minor +problems discovered in prior releases. +

2021-03-17 - Patch release 3.35.2

+Version 3.35.2 is a small patch release to fix some minor problems +that were discovered shortly after the 3.35.1 release. +

2021-03-15 - Patch release 3.35.1

+A user discovered an issue with the new DROP COLUMN capability +in version 3.35.0, and so version 3.35.1 was created to fix it. +No need to upgrade if you are not using DROP COLUMN. +

2021-03-12 - Release 3.35.0

+SQLite version 3.35.0 is a routine maintenance release. This +release adds a number of new language features, including +support for ALTER TABLE DROP COLUMN, built-in math functions, +generalized UPSERT, and the MATERIALIZED hint on common table +expressions. There are also query planner optimizations and +incremental CLI improvements. +

2020-01-20 - Release 3.34.1

+SQLite version 3.34.1 is a patch releases that fixes a possible +use-after-free bug that can be provoked by malicious SQL. Other +minor issues in extensions and documentation are also fixed. +

2020-12-01 - Release 3.34.0

+SQLite version 3.34.0 is a routine maintenance release. This +release adds incremental improvements to performance and features, +including enhancements to the query planner, multiple recursive +SELECTS in recursive common table expressions, and better error messages +from CHECK constraint failures. See the change log for details. +

2020-08-14 - Release 3.33.0

+SQLite version 3.33.0 is a routine maintenance release. This +release features added support for "UPDATE FROM" following the +PostgreSQL syntax, and a doubling of the maximum database size +to 281 TB, as well as many other improvements. See the change +log for details. +

2020-06-18 - Release 3.32.3

+The 3.32.3 release is a patch release that contains fixes for +various issues discovered by fuzzers. None of the issues fixed +are likely to be encountered by applications that use SQLite in +ordinary ways, though upgrading never hurts. +
+Map of all changes since the 3.32.0 release: +https://www.sqlite.org/src/timeline?p=version-3.32.3&bt=version-3.32.0 +

2020-06-04 - Release 3.32.2

+The 3.32.2 release is a one-line change relative to 3.32.1 +that fixes a long-standing bug in the COMMIT command. Since +version 3.17.0, if you were to retry a COMMIT command over +and over after it returns SQLITE_BUSY, it might eventually +report success, even though it was still blocked. This patch +fixes the problem. +

2020-05-25 - Release 3.32.1

+Grey-hats published +information about two SQLite bugs approximately 24 hours after +the release of version 3.32.0. These bugs enable maliciously +crafted SQL to crash the process that is running SQLite. Both +bugs are long-standing problems that affect releases prior to +3.32.0. The 3.32.1 release fixes both problems. +

2020-05-22 - Release 3.32.0

+Version 3.32.0 is an ordinary maintenance release of SQLite. +This release features the ability to run an +approximate ANALYZE to gather database statistics for +use by the query planner, without having to scan every row +of every index. +See the change log for additional enhancements +and improvements. +

2020-01-27 - Release 3.31.1

+Applications that use SQLite should only interface with SQLite +through the officially published APIs. Applications should not +depend upon or use the internal data structures of SQLite as those +structures might change from one release to another. However, there +is a popular application that does depend on the details of the +internal layout of data in an internal SQLite data structure, and +those details changed in version 3.31.0, breaking the application. +This is, technically, a bug in the application, not in SQLite. +But it is within the power of SQLite to fix it, by reverting the +internal data structure change, and so that is what we have done +for the 3.31.1 release. +

2020-01-22 - Release 3.31.0

+Version 3.31.0 is an ordinary maintenance release of SQLite. +This release features the ability to define +generated columns for tables as well as many other enhancements. +See the change log for additional information. +

2019-10-11 - Release 3.30.1

+Version 3.30.1 is a bug-fix release that addresses a problem +that can occur when an aggregate function in a nested query +makes use of the new FILTER clause capability. Some addition +patches for various obscure issues are also included, for +completeness. +

2019-10-04 - Release 3.30.0

+Version 3.30.0 is a regularly scheduled maintenance release +of SQLite containing miscellaneous performance and feature +enhancements. This release adds support fo the NULLS FIRST +and NULLS LAST clauses on ORDER BY statements and the +addition of FILTER clauses on all aggregate functions. +See the change log for details. +

2019-07-10 - Release 3.29.0

+Version 3.29.0 is a regularly scheduled maintenance release +of SQLite containing miscellaneous performance and feature +enhancements. See the change log for +details. +
+Beginning with this release, the +double-quoted string literal misfeature is deprecated. +The misfeature is still enabled by default, for legacy +compatibility, however developers are encouraged to +disable it at compile-time using the +-DSQLITE_DQS=0 option, or at run-time using +the SQLITE_DBCONFIG_DQS_DML and SQLITE_DBCONFIG_DQS_DDL +actions to the sqlite3_db_config() interface. This is +especially true for double-quoted string literals in +CREATE TABLE and CREATE INDEX statements, as those elements +can cause unexpected problems following an ALTER TABLE. +See ticket 9b78184be266fd70 +for an example. +

2019-04-16 - Release 3.28.0

+Version 3.28.0 is a regularly scheduled maintenance release +of SQLite containing miscellaneous performance and feature +enhancements. See the change log for +details. +
+This release fixes an obscure security issue. Applications +using older versions of SQLite may be vulnerable if +
+
SQLite is compiled with certain optional extensions + enabled, and +
the attacker is able to inject arbitrary SQL. +
+We are not aware of any applications that are vulnerable to +this problem. On the other hand, we do not know about +every application that uses SQLite. +If your application allows unauthenticated users on the internet +(and hence potential attackers) to run arbitrary SQL and if +you build SQLite with any of the optional extensions enabled, +then you should take this upgrade at your earliest opportunity. +
+For further information about improving SQLite's robustness +in internet-facing applications, see the our +security recommendations. +

2019-02-25 - Release 3.27.2

+Version 3.27.2 is a patch release that +fixes a two bugs and various documentation +errors found in the version 3.27.1. The +changes from version 3.27.1 and 3.27.0 are +minimal. +

2019-02-08 - Release 3.27.1

+After release 3.27.0 was tagged, but before the build could +be completed and uploaded, a +long-standing bug +in the query optimizer was reported via System.Data.SQLite. +Since people will be upgrading anyhow, we decided +publish the fix for this newly discovered problems right +away. Hence, 3.27.1 was released less than 24 hours after +3.27.0. +
+It would have been better if the query optimizer bug had come to +our attention one day earlier, so that we could have incorporated +a fix into 3.27.0, but sometimes that's the way things go. +

2019-02-07 - Release 3.27.0

+SQLite version 3.27.0 is a routine maintenance release with various +performance and feature enhancements. See the +release notes for details. +

2018-12-01 - Release 3.26.0

+SQLite version 3.26.0 is a routine maintenance release with various +performance and feature enhancements. See the +release notes for details. +

2018-11-05 - Release 3.25.3

+SQLite version 3.25.3 is a third patch against 3.25.0 that fixes various +problems that have come to light and which seem serious enough to +justify a patch. +

2018-09-25 - Release 3.25.2

+SQLite version 3.25.2 is another patch against 3.25.0 that fixes still +more problems associated with the new window function feature and the +ALTER TABLE enhancements. Of particular note is the new +PRAGMA legacy_alter_table=ON command, which causes the ALTER TABLE RENAME +command to behave in the same goofy way that it did before the enhancements +found in version 3.25.0 → references to renamed tables that are inside +the bodies of triggers and views are not updated. The legacy behavior is +arguably a bug, but some programs depend on the older buggy behavior. The +3.25.2 release also contains a fix to window function processing for +VIEWs. There also a slew of other minor fixes that affect obscure +compile-time options. See the +Fossil Timeline for +details. +

2018-09-18 - Release 3.25.1

+SQLite version 3.25.1 is a patch against version 3.25.0 that contains +two one-line fixes for bug that were introduced in version 3.25.0. +See the change log for details. Upgrading from 3.25.0 is recommended. +

2018-09-15 - Release 3.25.0

+SQLite version 3.25.0 is a regularly scheduled maintenance release. +Two big enhancements in this release: +
+
+Support for window functions was added, using the PostgreSQL documentation +as the baseline. +
+The ALTER TABLE command was enhanced to support renaming of columns, and +so that column and table renames are propagated into trigger bodies and views. +
+
In addition, there are various performance enhancements and minor fixes. +
One bug of note is +ticket 9936b2fa443fec +which describes a hard-to-reach condition where the ORDER BY LIMIT +optimization might cause an infinite loop during query evaluation. +This ticket raised a lot of +concern on +HackerNews and +Reddit, +probably due to my choice of the ticket +title. "Infinite Loop" sounds scary. But I argue that the bug isn't really +all that bad in that it is very difficult to reach, will show up during +testing (rather than magically appearing after a product is +deployed), does not cause any data loss, and does not return an +incorrect result. It was an important error, but not nearly as dire +as many people interpreted it to be. And, in any event, it is fixed now. +

2018-06-04 - Release 3.24.0

+SQLite version 3.24.0 is a regularly scheduled maintenance release. +Highlights of this release include support for PostgreSQL-style +UPSERT and improved performance, especially for ORDER BY LIMIT queries. +

2018-04-10 - Release 3.23.1

+The version 3.23.1 release fixes a bug in the new +LEFT JOIN strength reduction optimization added to version 3.23.0. +A few other minor and obscure fixes were also inserted, as well as +a small performance optimization. Code changes relative to +version 3.23.0 are minimal. +

2018-04-02 - Release 3.23.0

+The version 3.23.0 release is a regularly scheduled maintenance release. +See the change log for a list of enhancements and bug +fixes. +

2018-01-22 - Release 3.22.0

+The version 3.22.0 release is a regularly scheduled maintenance release. +There are many minor, though interesting, enhancements in this release. +See the change log for details. +

2017-10-24 - Release 3.21.0

+The version 3.21.0 release is a regularly scheduled maintenance release. +There are lots of enhancements in this release. +See the change log for details. +

2017-08-24 - Release 3.20.1

+The version 3.20.1 patch release changes two lines of code in +the sqlite3_result_pointer() interface in order to fix a rare +memory leak. There are no other changes relative to version 3.20.0. +

2017-08-01 - Release 3.20.0

+SQLite version 3.20.0 is a regularly scheduled maintenance release +of SQLite. +
+This release contains many minor enhancements, including: +
+
Several new extensions +
Enhancements to the "sqlite3.exe" command-line shell +
Query planner enhancements +
Miscellaneous code optimizations for improved performance +
Fixes for some obscure bugs +
+
+See the release notes for more information. +

2017-06-17 - Release 3.18.2

+SQLite version 3.18.2 is another backport of a bug fix found +in SQLite version 3.19.0, specifically the fix for +ticket 61fe9745. Changes +against version 3.18.0 are minimal. +

2017-06-16 - Release 3.18.1

+SQLite version 3.18.1 is a bug-fix release against version 3.18.0 +that fixes the auto_vacuum corruption bug described in ticket +fda22108. This release was +created for users who need that bug fix but do not yet want to upgrade +to version 3.19.3. +

2017-06-08 - Release 3.19.3

+Version 3.19.3 is an emergency patch release to fix a +bug in +auto_vacuum logic that can lead to database corruption. +The bug was introduced in version 3.16.0 +(2017-01-02). Though the bug is obscure and rarely +encountered, upgrading is recommended for all users, and +especially for users who turn on auto_vacuum. +

2017-05-25 - Release 3.19.2

+Still more problems have been found in the LEFT JOIN +flattening optimization +that was added in the 3.19.0 release. This patch release fixes all known +issues with that optimization and adds new test cases. Hopefully this +will be the last patch. +

2017-05-24 - Release 3.19.1

+One of the new query planner optimizations in the 3.19.0 release contained +bugs. The 3.19.1 patch release fixes them. +
+Beginning with 3.19.0, subqueries and views on the right-hand side of +a LEFT JOIN operator could sometimes be +flattened into the +main query. The new optimization worked well for all of the test cases +that the developers devised, and for millions of legacy test cases, but +once 3.19.0 was released, users found some other cases where the optimization +failed. Ticket +cad1ab4cb7b0fc344 contains +examples. +
+These problems exist only in 3.19.0. Users of SQLite 3.19.0 should +upgrade, but users of all prior versions of SQLite are safe. +

2017-05-22 - Release 3.19.0

+SQLite version 3.19.0 is a regularly scheduled maintenance release. +
+The emphasis on this release is improvements to the query planner. +There are also some obscure bug fixes. There is no reason to upgrade +unless you are having problems with a prior release. +

2017-03-30 - Release 3.18.0

+SQLite version 3.18.0 is a regularly scheduled maintenance release. +
+This release features an initial implementation the +"PRAGMA optimize" command. This command can now be used to cause +ANALYZE to be run on an as-needed basis. Applications should invoke +"PRAGMA optimize" just before closing the database connection. +The "PRAGMA optimize" statement will likely be enhanced to do other +kinds of automated database maintenance in future releases. +
+The Fossil version control system that is +used to manage the SQLite project has been upgraded to use SHA3-256 hashes +instead of SHA1. Therefore, the version identifications for SQLite now +show a 64-hex-digit SHA3-256 hash rather than the 40-hex-digit SHA1 hash. +
+See the change log for other enhancements and optimizations +in this release. +

2017-02-13 - Release 3.17.0

+SQLite version 3.17.0 is a regularly scheduled maintenance release. +
+Most of the changes in this release are performance optimizations. +Optimizations to the R-Tree extension are especially noticeable. +
+In this release, the default size of the +lookaside buffer allocated for each database connection +is increased from 64,000 to 120,000 bytes. This provides improved +performance on many common workloads in exchange for a small increase +in memory usage. +Applications that value a small memory footprint over raw speed +can change the lookaside buffer size back to its old value (or to zero) +using the SQLITE_DEFAULT_LOOKASIDE compile-time option, or the +sqlite3_config(SQLITE_CONFIG_LOOKASIDE) +start-time setting, or the +sqlite3_db_config(SQLITE_DBCONFIG_LOOKASIDE) +run-time setting. +

2017-01-06 - Release 3.16.2

+One of the performance optimizations added in 3.16.0 caused triggers +and foreign keys to malfunction for the REPLACE statement on +WITHOUT ROWID tables that lack secondary indexes. This patch +release fixes the problem. See ticket +30027b613b4 for details. +

2017-01-03 - Release 3.16.1

+SQLite version 3.16.1 fixes a bug in the row-value logic for UPDATE +statements inside of triggers. The bug has been there since row-values +were added by release 3.15.0, but was not discovered until just a few +minutes after the 3.16.0 release was published, and so it was not fixed +by 3.16.0. This patch release is version 3.16.0 with the row-value bug fix. +

2017-01-02 - Release 3.16.0

+SQLite version 3.16.0 is a regularly schedule maintenance release.
+ +
+This release includes many microoptimizations that collectively reduce +the CPU cycle count by about 9%, +add there have been important enhancements to the command-line shell.
+ +
Support for PRAGMA functions is added, +so that many pragma statements can be used as part of a larger SQL query. +This is considered an experimental feature. +We do not anticipate any changes to the PRAGMA function interface, but +will keep continue to call this interface "experimental" for a few release +cycles in case unforeseen issues arise.
+ +
See the change log for other enhancements. +

2016-11-28 - Release 3.15.2

+SQLite version 3.15.2 is a bug-fix patch release that fixes several minor +issues in the 3.15.0 and 3.15.1 releases. +

2016-11-04 - Release 3.15.1

+SQLite version 3.15.1 is a bug-fix patch release that fixes some minor +issues in the 3.15.0 release. +

2016-10-14 - Release 3.15.0

+SQLite version 3.15.0 is a regularly scheduled maintenance release. +The key feature in this release is the added support for +row values. There are also other enhancements and +fixes for a number of obscure bugs. +
+The 3.15.0 release uses about 7% fewer CPU cycles than 3.14.2. +Most of the improvement in this release +is in the SQL parser, query planner, and +byte-code generator (the front-end) corresponding +to the sqlite3_prepare_v2() interface. Overall, +version 3.15.0 uses about half as much CPU time as +version 3.8.1 (2013-10-17). These +performance measurements are made using the "speedtest1.c" +workload on x64 compiled with gcc and -Os. Performance +improvements may vary with different platforms and +workloads. +

2016-09-12 - Release 3.14.2

+SQLite version 3.14.2 fixes several obscure bugs and adds +improved support for building SQLite using the STDCALL calling +convention on 32-bit windows systems. Upgrading from versions +3.14 and 3.14.1 is optional. +

2016-08-11 - Release 3.14.1

+SQLite version 3.14.1 adds a small patch to improve the performance +of the pcache1TruncateUnsafe() routine for cases when the only a few +pages on the end of the cache are being removed. This causes COMMITs +to run faster when there is a very large page cache. Upgrading from +version 3.14 is optional. +

2016-08-08 - Release 3.14

+SQLite version 3.14 (the "π" release) +is a regularly scheduled maintenance +release containing performance enhancements, new features, and fixes for +obscure bugs. +

2016-05-18 - Release 3.13.0

+SQLite version 3.13.0 is a regularly schedule maintenance release containing +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. +

+ +Old news... + + -- cgit v1.2.3