*** DRAFT ***
SQLite Release 3.35.0 On 2021-03-30
- Added built-in SQL math functions().
- Added support for ALTER TABLE DROP COLUMN.
- Generalize UPSERT so that it supports multiple ON CONFLICT clauses
that are evaluated in order,
and so that if the final ON CONFLICT clause omits the conflict target
then the resolution can be DO UPDATE.
- Add support for the RETURNING clause on DELETE, INSERT, and
- Use less memory when running VACUUM on databases containing very large
TEXT or BLOB values. It is no longer necessary to hold the entire TEXT
or BLOB in memory all at once.
- Add support for the MATERIALIZED and NOT MATERIALIZED hints when
specifying common table expressions. The default behavior was
formerly NOT MATERIALIZED, but is now changed to MATERIALIZED for
CTEs that are used more than once.
- The SQLITE_DBCONFIG_ENABLE_TRIGGER setting is modified so that it only
controls triggers in the main database schema, not in the TEMP schema.
TEMP triggers are now always engaged.
- Query planner improvements:
- Enhancements to the min/max optimization so that it works better
with the IN operator and the OP_SeekScan optimization of the
- Attempt to process EXISTS operators in the WHERE clause as if
they were IN operators, in cases where this is a valid transformation
and seems likely to improve performance.
- Allow UNION ALL sub-queries to be flattened even if the parent query is a join.
- Use an index, if appropriate, on IS NOT NULL constraints, even if STAT4 is disabled.
- CLI enhancements:
- Enhance the ".stats" command to accept new arguments "stmt" and
"vmstep", causing prepare statement statistics and only the
virtual-machine step count to be shown, respectively.
- Add the ".filectrl data_version" command.
- Enhance the ".once" and ".output" commands so that if the destination argument
begins with "|" (indicating that output is redirected into a pipe) then the
argument does not need to be quoted.
- Bug fixes:
- Fix a potential NULL pointer dereference when processing a
syntactically incorrect SELECT statement with a correlated WHERE
clause and a "HAVING 0" clause. (Also fixed in the 3.34.1 patch release.)
- Fix a bug in the IN-operator optimization
of version 3.33.0 that can cause an incorrect answer.
- Fix incorrect answers from the LIKE operator if the pattern ends with "%" and there
is an "ESCAPE '_'" clause.
- SQLITE_SOURCE_ID: pending
- SHA3-256 for sqlite3.c: pending
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 ***