Visitar URL original
SQLite Release 3.53.3 On 2026-06-26
Small. Fast. Reliable.
Choose any three.

SQLite Release 3.53.3 On 2026-06-26

Prior changes from version 3.53.0 (2026-04-09):

  1. Fix the WAL-reset database corruption bug.
  2. Add the Query Result Formatter (QRF) library for formatting the results of SQL queries for human readability on a fixed-pitch font screen.
    1. Add the format method to the TCL Interface so that QRF is accessible from TCL.
    2. QRF is used for result formatting in the CLI, resulting in improved display capabilities.
  3. New SQL language features:
    1. Enhance ALTER TABLE to permit adding and removing NOT NULL and CHECK constraints.
    2. The REINDEX EXPRESSIONS statement rebuilds expression indexes. (Useful to repair stale expression indexes.)
    3. The body of TEMP triggers may now modify and/or query tables in the main schema.
    4. Enhance VACUUM INTO so that if a URI filename is used as the target and that filename has a reserve=N query parameter with N between 0 and 255, then the reserve amount for the generated database copy is set to N.
  4. New SQL functions:
    1. json_array_insert()
    2. jsonb_array_insert()
  5. Renovations to the CLI:
    1. Major enhancements to the .mode command.
    2. Improved result formatting, due to the addition of the QRF extension. For example, numeric values are now right-justified by default in tabular output modes.
    3. The default output mode for interactive CLI sessions now uses QRF to display query results in boxes formed using Unicode box-drawing characters, for improved legibility. Batch CLI sessions use the legacy output format for compatibility.
    4. Bare (unquoted) semicolons at the end of dot-commands are silently ignored.  ← Potential incompatibility!
    5. Fix the .testcase and .check commands so that they actually work, and use those commands in scripts that are part of the standard SQLite test suite included with the source tree.
    6. Command-line arguments that match *.sql or *.txt and are the names of non-empty files are read and interpreted as scripts of SQL statements and/or dot-commands.
    7. The argument to the ".timer" command can now be "once", to run the timer on only the next SQL statement.
    8. The new "--timeout S" option to the ".progress" dot-command causes SQL statements to interrupt after S seconds.
    9. The ".indexes" command was changed so that the PATTERN argument matches the name of the index, not the name of the table being indexed (thus making the PATTERN argument actually useful). And, several new options were added to ".indexes".
  6. New C-language interfaces:
    1. sqlite3_str_truncate()
    2. sqlite3_str_free()
    3. sqlite3_carray_bind_v2()
    4. Add the SQLITE_PREPARE_FROM_DDL option to sqlite3_prepare_v3() which permits virtual table implementations to safely prepare SQL statements that are derived from the database schema.
    5. Added the SQLITE_UTF8_ZT constant which can be used as the encoding parameter to sqlite3_result_text64() or sqlite3_bind_text64() to indicate that the value is UTF-8 encoded and zero terminated.
    6. The SQLITE_LIMIT_PARSER_DEPTH option is added to sqlite3_limit().
    7. The SQLITE_DBCONFIG_FP_DIGITS option is added to sqlite3_db_config(). See also item 9b below.
  7. Query planner improvements:
    1. Always use a sort-and-merge algorithm for EXCEPT, INTERSECT, and UNION, since this is almost always faster than using a hash table.
    2. Improvements to join order selection in large multi-way joins on a star schema.
    3. Enhance the EXISTS-to-JOIN optimization so that the inserted JOIN terms are not required to be on the inner-most loops, as long as all dependencies for the EXISTS-to-JOIN loops are in outer loops.
    4. Enhance the omit-noop-join optimization so that it is able to omit a chain of joins that do not affect the output.
    5. Allow queries that use "GROUP BY e1 ORDER BY e2" where e1 and e2 are identical apart from ASC/DESC sort-orders to be optimized using a single index.
    6. Allow virtual tables to optimize DISTINCT in cases where the result-set of a query does not exactly match the ORDER BY clause.
  8. Add new interfaces to the session extension that enable an application to add changes one at a time to the sqlite3_changegroup object:
    1. sqlite3changegroup_change_begin()
    2. sqlite3changegroup_change_blob()
    3. sqlite3changegroup_change_double()
    4. sqlite3changegroup_change_int64()
    5. sqlite3changegroup_change_null()
    6. sqlite3changegroup_change_text()
    7. sqlite3changegroup_change_finish()
    8. sqlite3changegroup_config()
  9. Improvements to floating-point ↔ text conversions.
    1. Reimplemented to improve performance.
    2. Rounding is now done by default to 17 significant digits, instead of 15, as was the case for all prior versions. The sqlite3_db_config(SQLITE_DBCONFIG_FP_DIGITS) API (item 6g above) can change this, if desired.
  10. Added the self-healing index feature to deal with the stale expression index problem.
  11. Add the "-p|--port" option to sqlite3_rsync.
  12. Discontinue support for Windows RT.
  13. JavaScript/WASM
    1. Add the "opfs-wl" VFS, functionally identical to the "opfs" VFS but using Web Locks for locking, which can promise fairer lock sharing than the "opfs" bespoke protocol can. "opfs-wl" requires Atomics.waitAsync(), so requires newer browsers than "opfs" does.

Prior changes from version 3.53.1 (2026-05-05):

  1. Fixes for problems in 3.53.1 reported by users. See the check-in timeline for details.

Prior changes from version 3.53.2 (2026-06-03):

  1. Fixes for problems in 3.53.0 reported by users. See the check-in timeline for details.

Changes in this specific patch release, version 3.53.3 (2026-06-26):

  1. Fixes for problems in 3.53.0 (and 3.53.1 and 3.53.2) mostly coming from AIs. See the check-in timeline for details.

    Hashes:

  2. SQLITE_SOURCE_ID: 2026-06-26 20:14:12 d4c0e51e4aeb96955b99185ab9cde75c339e2c29c3f3f12428d364a10d782c62
  3. SHA3-256 for sqlite3.c: 28e484abdaa43630e34040ef6ed92be973a1ad54107803d8af5145b889c23ed7

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.