Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Redate the 3.7.16.1 release to 2013-03-29. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
5d46117c19c0490b2c79405bf85e663c |
User & Date: | drh 2013-03-29 13:47:34.188 |
Context
2013-03-29
| ||
14:02 | Add source-id and sha1sum for version 3.7.16.1 (check-in: b6742f225c user: dan tags: trunk, version-3.7.16.1) | |
13:47 | Redate the 3.7.16.1 release to 2013-03-29. (check-in: 5d46117c19 user: drh tags: trunk) | |
12:17 | Fix a broken hyperlink in the different.html document. (check-in: e518038151 user: drh tags: trunk) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
38 39 40 41 42 43 44 | http://www.sqlite.org/src/timeline</a>.</p> } hd_close_aux hd_enable_main 1 } } | | | 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 | http://www.sqlite.org/src/timeline</a>.</p> } hd_close_aux hd_enable_main 1 } } chng {2013-03-29 (3.7.16.1)} { <li>Fix for a bug in the ORDER BY optimizer that was introduced in [version 3.7.15] which would sometimes optimize out the sorting step when in fact the sort was required. Ticket [http://www.sqlite.org/src/info/a179fe7465 | a179fe7465] <li>Fix a long-standing bug in the [CAST expression] that would recognize UTF16 characters as digits even if their most-significant-byte was not zero. Ticket [http://www.sqlite.org/src/info/689137afb6da41 | 689137afb6da41]. |
︙ | ︙ |
Changes to pages/news.in.
︙ | ︙ | |||
15 16 17 18 19 20 21 | 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%\">" } | | | | | | | 15 16 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 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 | 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 {2013-03-29} {Release 3.7.16.1} { SQLite [version 3.7.16.1] is a bug fix release that fixes a few problems that were present in the previous releases. The primary motivation for version 3.7.16.1 is to fix a bug in the query optimizer that was introduced as part of [version 3.7.15]. The query optimizer was being a little overzealous in optimizing out some ORDER BY clauses, which resulted in sorting being omitted on occasions where sorting is required to get the correct answer. See ticket [http://www.sqlite.org/src/info/a179fe7465 | a179fe7465] for details. In addition to the ORDER BY fix, several other patches to fix obscure (and mostly harmless) bugs and to fix spelling errors in source code comments are also included in this release. } newsitem {2013-03-18} {Release 3.7.16} { SQLite [version 3.7.16] is a regularly scheduled release of SQLite. This release contains several langauge enhancements and improvements to the query optimizer. A list of the major enhancements and optimizations can be see on the [version 3.7.16 | change log]. There was one important bug fix (see [http://www.sqlite.org/src/info/fc7bd6358f | Ticket fc7bd6358f]) that addresses an incorrect query result that could have occurred in a three-way join where the join constraints compared INTEGER columns to TEXT columns. This issue had been in the code for time out of mind and had never before been reported, so we surmise that it is very obscure. Nevertheless, all users are advised to upgrade to avoid any future problems associated with this issue. } newsitem {2013-01-09} {Release 3.7.15.2} { SQLite [version 3.7.15.2] is a patch release that fixes a single bug that was introduced in version [version 3.7.15]. The fix is a 4-character edit to a single line of code. Other than this 4-character change and the update of the version number, nothing has changed from [version 3.7.15.1]. } newsitem {2012-12-19} {Release 3.7.15.1} { SQLite [version 3.7.15.1] is a patch release that fixes a single bug that was introduced in version [version 3.7.15]. The fix involved changing two lines of code and adding a single assert(). This release also includes some new test cases to prevent a regression of the bug, and the version number is increased, of course. But otherwise, nothing has changed from [version 3.7.15]. } newsitem {2012-12-12} {Release 3.7.15} { SQLite [version 3.7.15] is a regularly schedule release of SQLite. This release contains several improvements to the query planner and optimizer and one important bug fix. This is the first release to officially support Windows 8 Phone. The important bug fix is a problem that can lead to segfaults when using [shared cache mode] on a schema that contains a [COLLATE operator] within |
︙ | ︙ | |||
102 103 104 105 106 107 108 | <li><p>Do a better job of recognizing when an ORDER BY clause can be implemented using indices - especially in cases where the ORDER BY clause contains terms from two or more tables in a join.</p> </ol> } | | | | 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 | <li><p>Do a better job of recognizing when an ORDER BY clause can be implemented using indices - especially in cases where the ORDER BY clause contains terms from two or more tables in a join.</p> </ol> } newsitem {2012-10-04} {Release 3.7.14.1} { SQLite [version 3.7.14.1] is a patch release. Changes from the baseline version 3.7.14 are minimal and are restricted to fixing three bugs. One of the fixed bugs is a long-standing issue with the TCL interface. Another is an external compiler bug that SQLite merely works around and that only comes up if you are using the VisualStudio-2012 compiler to generate WinRT applications on ARM with optimizations enabled. The third problem is an SQLite core bug, introduced in version 3.7.14, that can cause a segfault if a query contains a LEFT JOIN that contains an OR in the ON clause. } newsitem {2012-09-03} {Release 3.7.14} { SQLite [version 3.7.14] is a regularly scheduled maintenance release of SQLite. The previous release continues to work well. Upgrading is optional. Version 3.7.14 drops native support for OS/2. We are not aware of any active projects that were using SQLite on OS/2 and since the SQLite developers had no way of testing on OS/2 it seemed like it was time |
︙ | ︙ | |||
143 144 145 146 147 148 149 | This release also includes performance improvements to the sort algorithm that is used to implement ORDER BY and CREATE INDEX. And the query planner has been enhanced to better use covering indices on queries that use OR terms in the WHERE clause. } | | | 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 | This release also includes performance improvements to the sort algorithm that is used to implement ORDER BY and CREATE INDEX. And the query planner has been enhanced to better use covering indices on queries that use OR terms in the WHERE clause. } newsitem {2012-06-11} {Release 3.7.13} { SQLite [version 3.7.13] adds support for WinRT and metro style applications for Microsoft Windows 8. The 3.7.13 release is coming sooner than is usual after the previous release in order to get this new capability into the hands of developers. To use SQLite in a metro style application, compile with the -DSQLITE_OS_WINRT flag. Because of the increased application security and safety requirements of WinRT, all database |
︙ | ︙ | |||
175 176 177 178 179 180 181 | Getting these performance optimizations into circulation quickly is yet another reason for making this release so soon following the previous. The next release of SQLite is scheduled to occur after the usual 2 or 3 month interval. } | | | | 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 | Getting these performance optimizations into circulation quickly is yet another reason for making this release so soon following the previous. The next release of SQLite is scheduled to occur after the usual 2 or 3 month interval. } newsitem {2012-05-22} {Patch Release 3.7.12.1} { SQLite [version 3.7.12.1] is a patch release for [version 3.7.12] that fixes a [http://www.sqlite.org/src/info/c2ad16f997ee9c | bug] that was introduced in version 3.7.12 and that can cause a segfault for certain obscure nested aggregate queries. There are very few changes in 3.7.12.1, and upgrading is only needed for applications that do nested aggregate queries. } newsitem {2012-05-14} {Version 3.7.12} { SQLite [version 3.7.12] is a regularly scheduled maintenance release. This release contains several new optimizations and bug fixes and upgrading is recommended. See the [version 3.7.12 | change summary] for details. } </tcl> <a href="oldnews.html">Old news...</a> |