*** DRAFT ***

SQLite Release 3.32.2 On 2020-06-04

Prior changes from version 3.32.0 (2020-05-22):

  1. Added support for approximate ANALYZE using the PRAGMA analysis_limit command.
  2. Added the bytecode virtual table.
  3. Add the checksum VFS shim to the set of run-time loadable extensions included in the source tree.
  4. Added the iif() SQL function.
  5. 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.
  6. Added the sqlite3_create_filename(), sqlite3_free_filename(), and sqlite3_database_file_object() interfaces to better support of VFS shim implementations.
  7. Increase the default upper bound on the number of parameters from 999 to 32766.
  8. Added code for the UINT collating sequence as an optional loadable extension.
  9. Enhancements to the CLI:
    1. Add options to the .import command: --csv, --ascii, --skip
    2. The .dump command now accepts multiple LIKE-pattern arguments and outputs the union of all matching tables.
    3. Add the .oom command in debugging builds
    4. Add the --bom option to the .excel, .output, and .once commands.
    5. Enhance the .filectrl command to support the --schema option.
    6. The UINT collating sequence extension is automatically loaded
  10. The ESCAPE clause of a LIKE operator now overrides wildcard characters, so that the behavior matches what PostgreSQL does.

Prior changes from version 3.32.1 (2020-05-25):

  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.
  2. Other minor compiler-warning fixes and whatnot.

Changes in this specific patch release, version 3.32.2 (2020-06-04):

  1. 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

    Hashes:

  2. SQLITE_SOURCE_ID: 2020-06-04 12:58:43 ec02243ea6ce33b090870ae55ab8aa2534b54d216d45c4aa2fdbb00e86861e8c
  3. SHA3-256 for sqlite3.c: f17a2a57f7eebc72d405f3b640b4a49bcd02364a9c36e04feeb145eccafa3f8d

A complete list of SQLite releases in a single page and a chronology are both also available. A detailed history of every check-in is available at SQLite version control site.

*** DRAFT ***