Backwards-incompatible changes to some extensions in order to take
+ advantage of the improved security offered by the new
+ pointer passing interfaces:
+
+
Added the COMPLETION extension - designed to suggest
+ tab-completions for interactive user interfaces. This is a work in progress.
+ Expect further enhancements in future releases.
+
Added the PRAGMA secure_delete=FAST command. When secure_delete is
+ set to FAST, old content is overwritten with zeros as long as that does
+ not increase the amount of I/O. Deleted content might still persist on
+ the free-page list but will be purged from all b-tree pages.
+
Add support for tab-completion using the COMPLETION extension, for
+ both readline and linenoise.
+
Add the ".cd" command.
+
Enhance the ".schema" command to show the schema of all attached
+ databases.
+
Enhance ".tables" so that it shows the schema names for all attached
+ if the name is anything other than "main".
+
The ".import" command ignores an initial UTF-8 BOM.
+
Added the "--newlines" option to the ".dump" command to cause U+000a and
+ U+000d characters to be output literally rather than escaped using the
+ replace() function.
+
+
Query planner enhancements:
+
+
When generating individual loops for each ORed term of an OR scan,
+ move any constant WHERE expressions outside of the loop, as is
+ done for top-level loops.
+
The query planner examines the values of bound parameters to help
+ determine if a partial index is usable.
+
When deciding between two plans with the same estimated cost, bias
+ the selection toward the one that does not use the sorter.
+
Evaluate WHERE clause constraints involving correlated subqueries
+ last, in the hope that they never have be evaluated at all.
+
Do not use the flattening optimization for a sub-query on the RHS
+ of a LEFT JOIN if that subquery reads data from a virtual table as
+ doing so prevents the query planner from creating automatic indexes
+ on the results of the sub-query, which can slow down the query.
+
Miscellaneous optimizations result in a 2% reduction in CPU cycles used.
+
Bug Fixes:
+
Fix the behavior of sqlite3_column_name() for queries that use the
+ flattening optimization so that the result is consistent with other
+ queries that do not use that optimization, and with PostgreSQL, MySQL,
+ and SQLServer. Ticket de3403bf5ae.
+
Fix the query planner so that it knows not to use automatic indexes
+ on the right table of LEFT JOIN if the WHERE clause uses the IS operator.
+ Fix for ce68383bf6aba.
+
Ensure that the query planner knows that any column of a
+ flattened LEFT JOIN can be NULL even
+ if that column is labeled with "NOT NULL". Fix for ticket
+ 892fc34f173e99d8.
+