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.
+
+
Prior changes from version 3.16.1 (2017-01-03):
+
+
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.
+
+
Changes in this specific patch release, version 3.16.2 (2017-01-06):
+
+
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.
+