Small. Fast. Reliable.
Choose any three.

## SQLite Release 3.51.2 On 2026-01-09

Prior changes from version 3.51.0 (2025-11-04):

1. New macros in `sqlite3.h`:
   1. `SQLITE_SCM_BRANCH` → the name of the branch from which the source code is taken.
   2. `SQLITE_SCM_TAGS` → space-separated list of tags on the source code check-in.
   3. `SQLITE_SCM_DATETIME` → ISO-8601 date and time of the source code check-in.
2. Two new JSON functions, jsonb_each() and jsonb_tree() work the same as the existing json_each() and json_tree() functions except that they return JSONB for the "value" column when the "type" is 'array' or 'object'.
3. The carray and percentile extensions are now built into the amalgamation, though they are disabled by default and must be activated at compile-time using the -DSQLITE_ENABLE_CARRAY and/or -DSQLITE_ENABLE_PERCENTILE options, respectively.
4. Enhancements to TCL Interface:
   1. Add the `-asdict` flag to the `eval` command to have it set the row data as a dict instead of an array.
   2. User-defined functions may now `break` to return an SQL NULL.
5. CLI enhancements:
   1. Increase the precision of ".timer" to microseconds.
   2. Enhance the "box" and "column" formatting modes to deal with double-wide characters.
   3. The ".imposter" command provides read-only imposter tables that work with VACUUM and do not require the --unsafe-testing option.
   4. Add the --ifexists option to the CLI command-line option and to the .open command.
   5. Limit columns widths set by the ".width" command to 30,000 or less, as there is not good reason to have wider columns, but supporting wider columns provides opportunity to malefactors.
6. Performance enhancements:
   1. Use fewer CPU cycles to commit a read transaction.
   2. Early detection of joins that return no rows due to one or more of the tables containing no rows.
   3. Avoid evaluation of scalar subqueries if the result of the subquery does not change the result of the overall expression.
   4. Faster window function queries when using "`BETWEEN :x FOLLOWING AND :y FOLLOWING`" with a large :y.
7. Add the PRAGMA wal_checkpoint=NOOP; command and the SQLITE_CHECKPOINT_NOOP argument for sqlite3_wal_checkpoint_v2().
8. Add the sqlite3_set_errmsg() API for use by extensions.
9. Add the sqlite3_db_status64() API, which works just like the existing sqlite3_db_status() API except that it returns 64-bit results.
10. Add the SQLITE_DBSTATUS_TEMPBUF_SPILL option to the sqlite3_db_status() and sqlite3_db_status64() interfaces.
11. In the session extension add the sqlite3changeset_apply_v3() interface.
12. For the built-in printf() and the format() SQL function, omit the leading '-' from negative floating point numbers if the '+' flag is omitted and the "#" flag is present and all displayed digits are '0'. Use '%#f' or similar to avoid outputs like '-0.00' and instead show just '0.00'.
13. Improved error messages generated by FTS5.
14. Enforce STRICT typing on computed columns.
15. Improved support for VxWorks
16. JavaScript/WASM now supports 64-bit WASM. The canonical builds continue to be 32-bit but creating one's own 64-bit build is now as simple as running "make".
17. Improved resistance to database corruption caused by an application breaking Posix advisory locks using close().

Prior changes from version 3.51.1 (2025-11-28):

1. Fix incorrect results from nested EXISTS queries caused by the optimization in item 6b in the 3.51.0 release.
2. Fix a latent bug in fts5vocab virtual table, exposed by new optimizations in the 3.51.0 release

Changes in this specific patch release, version 3.51.2 (2026-01-09):

1. Fix an obscure deadlock in the new broken-posix-lock detection logic in item 17 above.
2. Fix multiple problems in the EXISTS-to-JOIN optimization that was added as part of optimization item 6b above.
3. Other minor bug fixes.
4. SQLITE_SOURCE_ID: 2026-01-09 17:27:48 b270f8339eb13b504d0b2ba154ebca966b7dde08e40c3ed7d559749818cb2075
5. SHA3-256 for sqlite3.c: 733b3fcc6cccb1e334424b9b91a9d68b618385b76ebfcbb106690bd3a9e61367

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.