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.
+
Rename the printf() SQL function to format() for better
+ compatibility. The original printf() name is retained as an alias
+ for backwards compatibility.
+
Added the sqlite3_error_offset() interface, which can sometimes
+ help to localize an SQL error to a specific character in the input
+ SQL text, so that applications can provide better error messages.
+
Enhanced the interface to virtual tables as follows:
+
+
Added the sqlite3_vtab_in() interface (and related) to enable
+ a virtual table to process IN operator constraints all at once,
+ rather than processing each value of the right-hand side of the
+ IN operator separately.
+
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.
+
+
+
Prior changes from version 3.38.2 (2022-03-26):
+
+
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.
+
+
+
Prior changes from version 3.38.3 (2022-04-27):
+
+
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.
+
+
+
Changes in this specific patch release, version 3.38.4 (2022-05-04):
+
+
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.
+
+