Documentation Source Text

Check-in [4a562f8d21]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Change log updates due to review of sqlite3.c diffs from prior release.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 4a562f8d21958e3ca2f61db0eb32c90abfab593b8e94b8577dd6288135a30d00
User & Date: drh 2018-05-29 15:55:30.318
Context
2018-05-29
18:35
Document (with links) that SQLite is a LoC Recommended Storage Format. (check-in: 2ab12e598f user: drh tags: trunk)
15:55
Change log updates due to review of sqlite3.c diffs from prior release. (check-in: 4a562f8d21 user: drh tags: trunk)
2018-05-26
01:59
Show the apSqlParam field that was added to the sqlite3_rtree_query_info object in version 3.8.11. (check-in: b5582fa868 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/changes.in.
︙︙
58
59
60
61
62
63
64


65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80



81
82
83
84
85
86
87

<li> The [OR optimization] is allowed to proceed
     even if the OR expression has also been converted into an IN
     expression.  Uses of the OR optimization are now also 
     [eqp-or-opt|more clearly shown] in the [EXPLAIN QUERY PLAN] output.
<li> The query planner is more aggressive about using
     [automatic indexes] for views and subqueries for which it is
     not possible to create a persistent index.


<li> Performance improvements in the LEMON-generated parser.
<p><b>Bug fixes:</b>
<li> For the right-hand table of a LEFT JOIN, compute the values
     of expressions directly rather than loading precomputed values
     out of an [expression index] as the expression index might
     not contain the correct value.  Ticket
     [https://sqlite.org/src/info/7fa8049685b50b5aeb0c2|7fa8049685b50b5aeb0c2]
<li> Do not attempt to use terms from the WHERE clause to enable
     indexed lookup of the right-hand table of a LEFT JOIN.  Ticket
     [https://sqlite.org/src/info/4ba5abf65c5b0f9a96a7a|4ba5abf65c5b0f9a96a7a]
<li> Fix a memory leak that can occur following a failure to open error
     in the [CSV virtual table]
<li> Fix a long-standing problem wherein a corrupt schema on the
     [sqlite_sequence] table used by [AUTOINCREMENT] can lead to
     a crash. Ticket
     [https://www.sqlite.org/src/info/d8dc2b3a58cd5dc29|d8dc2b3a58cd5dc2918a1]



<p><b>Hashes:</b>
<li>SQLITE_SOURCE_ID: <i>pending</i>
<li>SHA3-256 for sqlite3.c: <i>pending</i>
}


chng {2018-04-10 (3.23.1)} {








>
>
















>
>
>








58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92

<li> The [OR optimization] is allowed to proceed
     even if the OR expression has also been converted into an IN
     expression.  Uses of the OR optimization are now also 
     [eqp-or-opt|more clearly shown] in the [EXPLAIN QUERY PLAN] output.
<li> The query planner is more aggressive about using
     [automatic indexes] for views and subqueries for which it is
     not possible to create a persistent index.
<li> Make use of the one-pass UPDATE and DELETE query plans in the
     [R-Tree extension] where appropriate.
<li> Performance improvements in the LEMON-generated parser.
<p><b>Bug fixes:</b>
<li> For the right-hand table of a LEFT JOIN, compute the values
     of expressions directly rather than loading precomputed values
     out of an [expression index] as the expression index might
     not contain the correct value.  Ticket
     [https://sqlite.org/src/info/7fa8049685b50b5aeb0c2|7fa8049685b50b5aeb0c2]
<li> Do not attempt to use terms from the WHERE clause to enable
     indexed lookup of the right-hand table of a LEFT JOIN.  Ticket
     [https://sqlite.org/src/info/4ba5abf65c5b0f9a96a7a|4ba5abf65c5b0f9a96a7a]
<li> Fix a memory leak that can occur following a failure to open error
     in the [CSV virtual table]
<li> Fix a long-standing problem wherein a corrupt schema on the
     [sqlite_sequence] table used by [AUTOINCREMENT] can lead to
     a crash. Ticket
     [https://www.sqlite.org/src/info/d8dc2b3a58cd5dc29|d8dc2b3a58cd5dc2918a1]
<li> Fix the [json_each()] function so that it returns
     valid results on its "fullkey" column when the input is a simple value
     rather than an array or object.
<p><b>Hashes:</b>
<li>SQLITE_SOURCE_ID: <i>pending</i>
<li>SHA3-256 for sqlite3.c: <i>pending</i>
}


chng {2018-04-10 (3.23.1)} {
︙︙