Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add a report of the SEE corruption bug to the 3.9.0 release notes. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
8b38705a3d8375c982ba204628545811 |
User & Date: | drh 2015-10-09 15:46:12.720 |
Context
2015-10-10
| ||
09:36 | Add a new example for external-content tables to fts3.html. (check-in: e68ac068e8 user: dan tags: trunk) | |
2015-10-09
| ||
15:46 | Add a report of the SEE corruption bug to the 3.9.0 release notes. (check-in: 8b38705a3d user: drh tags: trunk) | |
15:01 | Keep FTS5 experimental for at least one more release cycle. (check-in: 7ef90a2dde user: drh tags: trunk) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
46 47 48 49 50 51 52 | WITHOUT ROWID tables. <li>Enhance the [dbstat virtual table] so that it can be used as a [table-valued functions] where the argument is the schema to be analyzed. <p><b>Other changes:</b> <li>The [sqlite3_memory_alarm()] interface, which has been deprecated and undocumented for 8 years, is changed into a no-op. | | > > > > | 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 | WITHOUT ROWID tables. <li>Enhance the [dbstat virtual table] so that it can be used as a [table-valued functions] where the argument is the schema to be analyzed. <p><b>Other changes:</b> <li>The [sqlite3_memory_alarm()] interface, which has been deprecated and undocumented for 8 years, is changed into a no-op. <p><b>Important fixes:</b> <li>Fixed a critical bug in the [https://www.sqlite.org/see/doc/trunk/www/readme.wiki|SQLite Encryption Extension] that could cause the database to become unreadable and unrecoverable if a [VACUUM] command changed the size of the encryption nonce. <li>Added a memory barrier in the implementation of [sqlite3_initialize()] to help ensure that it is thread-safe. <li>Fix the [OR optimization] so that it always ignores subplans that do not use an index. <li>Do not apply the WHERE-clause pushdown optimization on terms that originate in the ON or USING clause of a LEFT JOIN. Fix for ticket [https://www.sqlite.org/src/info/c2a19d81652f40568c|c2a19d81652f40568c]. |
︙ | ︙ |