Documentation Source Text

  incr nChng
}

chng {2017-05-24 (3.19.1)} {
<li>Fix a bug in the LEFT JOIN flattener optimization.
    (see ticket [https://www.sqlite.org/src/info/cad1ab4cb7b0fc|cad1ab4cb7b0fc])
<li>Remove a surplus semicolon that was causing problems for older versions of MSVC.



} {patchagainst 1}

chng {2017-05-22 (3.19.0)} {
<li> The [SQLITE_READ] [authorizer callback] is invoked once
     with a column name that is an empty string
     for every table referenced in a query from which no columns are extracted.
<li> When using an index on an expression, try to use expression values already

  incr nChng
}

chng {2017-05-24 (3.19.1)} {
<li>Fix a bug in the LEFT JOIN flattener optimization.
    (see ticket [https://www.sqlite.org/src/info/cad1ab4cb7b0fc|cad1ab4cb7b0fc])
<li>Remove a surplus semicolon that was causing problems for older versions of MSVC.
<p><b>Hashes:</b>
<li>SQLITE_SOURCE_ID: "2017-05-24 13:08:33 f6d7b988f40217821a382bc298180e9e6794f3ed79a83c6ef5cae048989b3f86"
<li>SHA3-256 for sqlite3.c: 996b2aff37b6e0c6663d0312cd921bbdf6826c989cbbb07dadde5e9672889bca
} {patchagainst 1}

chng {2017-05-22 (3.19.0)} {
<li> The [SQLITE_READ] [authorizer callback] is invoked once
     with a column name that is an empty string
     for every table referenced in a query from which no columns are extracted.
<li> When using an index on an expression, try to use expression values already

#    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 {
xxxxxxxxxx|2017-05-24|version 3.19.1
28a94eb282|2017-05-22|version 3.19.0
424a0d3803|2017-03-28|version 3.18.0
ada05cfa86|2017-02-13|version 3.17.0
a65a62893c|2017-01-06|version 3.16.2
979f043928|2017-01-03|Version 3.16.1
04ac0b75b1|2017-01-02|Version 3.16.0
bbd85d235f|2016-11-28|Version 3.15.2

#    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 {
f6d7b988f4|2017-05-24|version 3.19.1
28a94eb282|2017-05-22|version 3.19.0
424a0d3803|2017-03-28|version 3.18.0
ada05cfa86|2017-02-13|version 3.17.0
a65a62893c|2017-01-06|version 3.16.2
979f043928|2017-01-03|Version 3.16.1
04ac0b75b1|2017-01-02|Version 3.16.0
bbd85d235f|2016-11-28|Version 3.15.2

  hd_puts "<h3>$date - $title</h3>"
  regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt
  regsub -all {[Tt]icket #(\d+)} $txt \
      {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} txt
  hd_resolve "<blockquote>$txt</blockquote>"
  hd_puts "<hr width=\"50%\">"
}



















newsitem {2017-05-22} {Release 3.19.0} {
SQLite [version 3.19.0] is a regularly scheduled maintenance release.
<p>
The emphasis on this release is improvements to the query planner.
There are also some obscure bug fixes.  There is no reason to upgrade
unless you are having problems with a prior release.

  hd_puts "<h3>$date - $title</h3>"
  regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt
  regsub -all {[Tt]icket #(\d+)} $txt \
      {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} txt
  hd_resolve "<blockquote>$txt</blockquote>"
  hd_puts "<hr width=\"50%\">"
}

newsitem {2017-05-24} {Release 3.19.1} {
One of the new query planner optimizations in the 3.19.0 release contained
bugs.  The 3.19.1 patch release fixes them.
<p>
Beginning with 3.19.0, subqueries and views on the right-hand side of
a LEFT JOIN operator could sometimes be
[https://sqlite.org/optoverview.html#flattening|flattened] into the
main query.  The new optimization worked well for all of the test cases
that the developers devised, and for millions of legacy test cases, but
once 3.19.0 was released, users found some other cases where the optimization
failed.  Ticket
[https://sqlite.org/src/info/cad1ab4cb7b0fc344|cad1ab4cb7b0fc344] contains
examples.
<p>
These problems exist only in 3.19.0.  Users of SQLite 3.19.0 should
upgrade, but users of all prior versions of SQLite are safe.
}

newsitem {2017-05-22} {Release 3.19.0} {
SQLite [version 3.19.0] is a regularly scheduled maintenance release.
<p>
The emphasis on this release is improvements to the query planner.
There are also some obscure bug fixes.  There is no reason to upgrade
unless you are having problems with a prior release.