Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix another release note typo. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: | 4020461a82e47f80fca26c2938c2a3be |
| User & Date: | drh 2017-05-22 19:38:22 |
Context
|
2017-05-22
| ||
| 20:01 | Fix typo and clarify wording in the new faster-than-filesystem update. check-in: 2912902889 user: drh tags: trunk | |
| 19:38 | Fix another release note typo. check-in: 4020461a82 user: drh tags: trunk | |
| 19:28 | Fix typo in the 3.19.0 release notes. check-in: 76f5154a37 user: drh tags: trunk | |
Changes
Changes to pages/changes.in.
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 |
<li> Enhance the [flattening optimization] so that it is able to flatten views
on the right-hand side of a LEFT JOIN.
<li> Use [replace()] instead of [char()] for escaping newline and carriage-return
characters embedded in strings in the .dump output from the [command-line shell].
<li> Avoid unnecessary foreign key processing in UPDATE statements that do not
touch the columns that are constrained by the foreign keys.
<li> On a DISTINCT query that uses an index, try to skip ahead to the next distinct
entry using the index rather that stepping through rows, when an appropriate
index is available.
<li> Avoid unnecessary invalidation of [sqlite3_blob] handles when making
changes to unrelated tables.
<li> Transfer any terms of the HAVING clause that use only columns mentioned in
the GROUP BY clause over to the WHERE clause for faster processing.
<li> Reuse the same materialization of a VIEW if that VIEW appears more than
once in the same query.
|
| |
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 |
<li> Enhance the [flattening optimization] so that it is able to flatten views
on the right-hand side of a LEFT JOIN.
<li> Use [replace()] instead of [char()] for escaping newline and carriage-return
characters embedded in strings in the .dump output from the [command-line shell].
<li> Avoid unnecessary foreign key processing in UPDATE statements that do not
touch the columns that are constrained by the foreign keys.
<li> On a DISTINCT query that uses an index, try to skip ahead to the next distinct
entry using the index rather than stepping through rows, when an appropriate
index is available.
<li> Avoid unnecessary invalidation of [sqlite3_blob] handles when making
changes to unrelated tables.
<li> Transfer any terms of the HAVING clause that use only columns mentioned in
the GROUP BY clause over to the WHERE clause for faster processing.
<li> Reuse the same materialization of a VIEW if that VIEW appears more than
once in the same query.
|