Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Adjust the change log and hashes for the 3.16.2 release. |
---|---|
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
140541287d173ee790d2d61b713e48e8 |
User & Date: | drh 2017-01-06 16:36:53 |
Context
2017-01-06
| ||
16:48 | Change the date of the news.html entry for 3.16.2 to 2017-01-06. check-in: 4cd739c3eb user: dan tags: trunk | |
16:36 | Adjust the change log and hashes for the 3.16.2 release. check-in: 140541287d user: drh tags: trunk | |
2017-01-05
| ||
17:53 | Changes for the 3.16.2 release. check-in: dea27852a0 user: drh tags: trunk | |
Changes
Changes to pages/changes.in.
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
..
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
proc chng {date desc {options {}}} { global nChng aChng xrefChng set aChng($nChng) [list $date $desc $options] set xrefChng($date) $nChng incr nChng } chng {2017-01-05 (3.16.2)} { <li>Fix the [REPLACE] statement for [WITHOUT ROWID] tables that lack secondary indexes so that it works correctly with triggers and foreign keys. This was a new bug caused by performance optimizations added in version 3.16.0. Ticket [https://www.sqlite.org/src/info/30027b613b4|30027b613b4] <li>Fix the [sqlite3_value_text()] interface so that it correctly translates content generated by [zeroblob()] into a string of all ................................................................................ 0x00 characters. This is a long-standing issue discovered after the 3.16.1 release by [https://github.com/google/oss-fuzz|OSS-Fuzz] <li>Fix the bytecode generator to deal with a subquery in the FROM clause that is itself a UNION ALL where one side of the UNION ALL is a view that contains an ORDER BY. This is a long-standing issue that was discovered after the release of 3.16.1. See ticket [https://www.sqlite.org/src/info/190c2507|190c2507]. <p><b>Hashes:</b> <li>SQLITE_SOURCE_ID: "2017-01-05 17:27:12 285c5a54dd4f872ba98c5cd1bd3d61ae1360930f" <li>SHA1 for sqlite3.c: 66083bdd3626386c3d0af3213c26f8e21dbe8a73 } {patchagainst 1 patchagainst 2} chng {2017-01-03 (3.16.1)} { <li>Fix a bug concerning the use of [row values] within [CREATE TRIGGER|triggers] (see ticket [https://www.sqlite.org/src/info/8c9458e7|8c9458e7]) that was in version 3.15.0 but was not reported until moments after the 3.16.0 release was published. |
|
>
>
>
>
|
|
|
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
..
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
proc chng {date desc {options {}}} { global nChng aChng xrefChng set aChng($nChng) [list $date $desc $options] set xrefChng($date) $nChng incr nChng } chng {2017-01-06 (3.16.2)} { <li>Fix the [REPLACE] statement for [WITHOUT ROWID] tables that lack secondary indexes so that it works correctly with triggers and foreign keys. This was a new bug caused by performance optimizations added in version 3.16.0. Ticket [https://www.sqlite.org/src/info/30027b613b4|30027b613b4] <li>Fix the [sqlite3_value_text()] interface so that it correctly translates content generated by [zeroblob()] into a string of all ................................................................................ 0x00 characters. This is a long-standing issue discovered after the 3.16.1 release by [https://github.com/google/oss-fuzz|OSS-Fuzz] <li>Fix the bytecode generator to deal with a subquery in the FROM clause that is itself a UNION ALL where one side of the UNION ALL is a view that contains an ORDER BY. This is a long-standing issue that was discovered after the release of 3.16.1. See ticket [https://www.sqlite.org/src/info/190c2507|190c2507]. <li>Adjust the [sqlite3_column_count()] API so it more often returns the same values for [PRAGMA] statements as it did in prior releases, to minimize disruption to applications that might be using that interface in unexpected ways. <p><b>Hashes:</b> <li>SQLITE_SOURCE_ID: "2017-01-06 16:32:41 a65a62893ca8319e89e48b8a38cf8a59c69a8209" <li>SHA1 for sqlite3.c: 2bebdc3f24911c0d12b6d6c0123c3f84d6946b08 } {patchagainst 1 patchagainst 2} chng {2017-01-03 (3.16.1)} { <li>Fix a bug concerning the use of [row values] within [CREATE TRIGGER|triggers] (see ticket [https://www.sqlite.org/src/info/8c9458e7|8c9458e7]) that was in version 3.15.0 but was not reported until moments after the 3.16.0 release was published. |
Changes to pages/chronology.in.
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 |
# ORDER BY mtime DESC; # # A small amount of manual editing and de-duplication followed. # # Manually edit the list for each subsequent release. # foreach line [split { 285c5a54dd|2016-01-05|version 3.16.2 979f043928|2016-01-03|Version 3.16.1 04ac0b75b1|2017-01-02|Version 3.16.0 bbd85d235f|2016-11-28|Version 3.15.2 1136863c76|2016-11-04|Version 3.15.1 707875582f|2016-10-14|Version 3.15.0 29dbef4b85|2016-09-12|Version 3.14.2 a12d805977|2016-08-11|Version 3.14.1 |
| |
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 |
# ORDER BY mtime DESC; # # A small amount of manual editing and de-duplication followed. # # Manually edit the list for each subsequent release. # foreach line [split { a65a62893c|2016-01-06|version 3.16.2 979f043928|2016-01-03|Version 3.16.1 04ac0b75b1|2017-01-02|Version 3.16.0 bbd85d235f|2016-11-28|Version 3.15.2 1136863c76|2016-11-04|Version 3.15.1 707875582f|2016-10-14|Version 3.15.0 29dbef4b85|2016-09-12|Version 3.14.2 a12d805977|2016-08-11|Version 3.14.1 |