Documentation Source Text

Check-in [522b8714da]
Login

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

Overview
Comment:Version 3.19.1
Timelines: family | ancestors | descendants | both | trunk | release | version-3.19.1
Files: files | file ages | folders
SHA3-256: 522b8714da4be72b7e284067eb2de3f31b14b6720d4c88582e3ec2fa6ead20e2
User & Date: drh 2017-05-24 13:18:20
Context
2017-05-25
00:40
Initial changes for the 3.19.2 release. check-in: 21ff2eb546 user: drh tags: trunk
2017-05-24
13:18
Version 3.19.1 check-in: 522b8714da user: drh tags: trunk, release, version-3.19.1
2017-05-23
12:49
Start a change log for the 3.19.1 patch release. check-in: 3abd703937 user: drh tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to pages/changes.in.

    21     21     incr nChng
    22     22   }
    23     23   
    24     24   chng {2017-05-24 (3.19.1)} {
    25     25   <li>Fix a bug in the LEFT JOIN flattener optimization.
    26     26       (see ticket [https://www.sqlite.org/src/info/cad1ab4cb7b0fc|cad1ab4cb7b0fc])
    27     27   <li>Remove a surplus semicolon that was causing problems for older versions of MSVC.
           28  +<p><b>Hashes:</b>
           29  +<li>SQLITE_SOURCE_ID: "2017-05-24 13:08:33 f6d7b988f40217821a382bc298180e9e6794f3ed79a83c6ef5cae048989b3f86"
           30  +<li>SHA3-256 for sqlite3.c: 996b2aff37b6e0c6663d0312cd921bbdf6826c989cbbb07dadde5e9672889bca
    28     31   } {patchagainst 1}
    29     32   
    30     33   chng {2017-05-22 (3.19.0)} {
    31     34   <li> The [SQLITE_READ] [authorizer callback] is invoked once
    32     35        with a column name that is an empty string
    33     36        for every table referenced in a query from which no columns are extracted.
    34     37   <li> When using an index on an expression, try to use expression values already

Changes to pages/chronology.in.

    24     24   #    ORDER BY mtime DESC;
    25     25   #
    26     26   # A small amount of manual editing and de-duplication followed.
    27     27   #
    28     28   # Manually edit the list for each subsequent release.
    29     29   #      
    30     30   foreach line [split {
    31         -xxxxxxxxxx|2017-05-24|version 3.19.1
           31  +f6d7b988f4|2017-05-24|version 3.19.1
    32     32   28a94eb282|2017-05-22|version 3.19.0
    33     33   424a0d3803|2017-03-28|version 3.18.0
    34     34   ada05cfa86|2017-02-13|version 3.17.0
    35     35   a65a62893c|2017-01-06|version 3.16.2
    36     36   979f043928|2017-01-03|Version 3.16.1
    37     37   04ac0b75b1|2017-01-02|Version 3.16.0
    38     38   bbd85d235f|2016-11-28|Version 3.15.2

Changes to pages/news.in.

    14     14     hd_puts "<h3>$date - $title</h3>"
    15     15     regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt
    16     16     regsub -all {[Tt]icket #(\d+)} $txt \
    17     17         {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} txt
    18     18     hd_resolve "<blockquote>$txt</blockquote>"
    19     19     hd_puts "<hr width=\"50%\">"
    20     20   }
           21  +
           22  +newsitem {2017-05-24} {Release 3.19.1} {
           23  +One of the new query planner optimizations in the 3.19.0 release contained
           24  +bugs.  The 3.19.1 patch release fixes them.
           25  +<p>
           26  +Beginning with 3.19.0, subqueries and views on the right-hand side of
           27  +a LEFT JOIN operator could sometimes be
           28  +[https://sqlite.org/optoverview.html#flattening|flattened] into the
           29  +main query.  The new optimization worked well for all of the test cases
           30  +that the developers devised, and for millions of legacy test cases, but
           31  +once 3.19.0 was released, users found some other cases where the optimization
           32  +failed.  Ticket
           33  +[https://sqlite.org/src/info/cad1ab4cb7b0fc344|cad1ab4cb7b0fc344] contains
           34  +examples.
           35  +<p>
           36  +These problems exist only in 3.19.0.  Users of SQLite 3.19.0 should
           37  +upgrade, but users of all prior versions of SQLite are safe.
           38  +}
    21     39   
    22     40   newsitem {2017-05-22} {Release 3.19.0} {
    23     41   SQLite [version 3.19.0] is a regularly scheduled maintenance release.
    24     42   <p>
    25     43   The emphasis on this release is improvements to the query planner.
    26     44   There are also some obscure bug fixes.  There is no reason to upgrade
    27     45   unless you are having problems with a prior release.