Documentation Source Text

Check-in [ee711c5d19]
Login

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

Overview
Comment:Add SOURCE_ID and sha1sum for version 3.13.0.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk | version-3.13.0
Files: files | file ages | folders
SHA1: ee711c5d195da646c5513d506fb50ff7d1ae392e
User & Date: dan 2016-05-18 11:04:04.842
Context
2016-05-19
12:19
Add the Da Rocha book to the books.html page. (check-in: 5b4b8cea40 user: drh tags: trunk)
2016-05-18
11:04
Add SOURCE_ID and sha1sum for version 3.13.0. (check-in: ee711c5d19 user: dan tags: trunk, version-3.13.0)
10:55
Last update to News and Changes prior to release. (check-in: c71ec9449d user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/changes.in.
︙︙
51
52
53
54
55
56
57



58
59
60
61
62
63
64

    but none of the indexes reference any table columns other than the INTEGER PRIMARY KEY.
    Ticket [https://www.sqlite.org/src/info/16c9801ceba49|16c9801ceba49].
<li>When checking for the WHERE-clause push-down optimization, verify that all terms
    of the compound inner SELECT are non-aggregate, not just the last term. Fix for ticket
    [https://www.sqlite.org/src/info/f7f8c97e97597|f7f8c97e97597].
<li>Fix a locking race condition in Windows that can occur when two or more processes
    attempt to recover the same [hot journal] at the same time.



} {backport {2016-04-18 (3.12.2)} backport {2016-04-08 (3.12.1)}}

chng {2016-04-18 (3.12.2)} {
<li>Fix a backwards compatibility problem in version 3.12.0 and 3.12.1:
    Columns declared as <tt>"INTEGER" PRIMARY KEY</tt> (with quotes around
    the datatype keyword) were not being recognized as an
    [INTEGER PRIMARY KEY], which resulted in an incompatible database file.








>
>
>








51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

    but none of the indexes reference any table columns other than the INTEGER PRIMARY KEY.
    Ticket [https://www.sqlite.org/src/info/16c9801ceba49|16c9801ceba49].
<li>When checking for the WHERE-clause push-down optimization, verify that all terms
    of the compound inner SELECT are non-aggregate, not just the last term. Fix for ticket
    [https://www.sqlite.org/src/info/f7f8c97e97597|f7f8c97e97597].
<li>Fix a locking race condition in Windows that can occur when two or more processes
    attempt to recover the same [hot journal] at the same time.
<p><b>Hashes:</b>
<li>SQLITE_SOURCE_ID: "2016-05-18 10:57:30 fc49f556e48970561d7ab6a2f24fdd7d9eb81ff2"
<li>SHA1 for sqlite3.c: 9b9171b1e6ce7a980e6b714e9c0d9112657ad552
} {backport {2016-04-18 (3.12.2)} backport {2016-04-08 (3.12.1)}}

chng {2016-04-18 (3.12.2)} {
<li>Fix a backwards compatibility problem in version 3.12.0 and 3.12.1:
    Columns declared as <tt>"INTEGER" PRIMARY KEY</tt> (with quotes around
    the datatype keyword) were not being recognized as an
    [INTEGER PRIMARY KEY], which resulted in an incompatible database file.
︙︙