Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Update News and the change log. Bring the release date forward to 2014-02-03. Fix typos. Move older news entries out to oldnews.in. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
ea6e1d11de14e99e1935f34dfc038d03 |
User & Date: | drh 2014-01-29 17:47:45.602 |
Context
2014-01-30
| ||
11:08 | Clarification of the role of ORDER BY and LIMIT in compound SELECT statements. (check-in: 7b8d43a8ef user: drh tags: trunk) | |
2014-01-29
| ||
17:47 | Update News and the change log. Bring the release date forward to 2014-02-03. Fix typos. Move older news entries out to oldnews.in. (check-in: ea6e1d11de user: drh tags: trunk) | |
17:10 | Add new elements to the 3.8.3 change log. (check-in: 7ab25ac60e user: drh tags: trunk) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
14 15 16 17 18 19 20 | set nChng 0 proc chng {date desc {options {}}} { global nChng aChng set aChng($nChng) [list $date $desc $options] incr nChng } | | | 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 | set nChng 0 proc chng {date desc {options {}}} { global nChng aChng set aChng($nChng) [list $date $desc $options] incr nChng } chng {2014-02-03 (3.8.3)} { <li>Added support for [common table expressions] and the [WITH clause]. <li>Added the [printf()] SQL function. <li>Added [SQLITE_DETERMINISTIC] as an optional bit in the 4th argument to the [sqlite3_create_function()] and related interfaces, providing applications with the ability to create new functions that can be factored out of inner loops when they have constant arguments. <li>Add [SQLITE_READONLY_DBMOVED] error code, returned at the beginning of a |
︙ | ︙ |
Changes to pages/compile.in.
︙ | ︙ | |||
939 940 941 942 943 944 945 946 947 948 949 950 951 952 | cause a parse error. An [INSERT] statement with multiple values in the VALUES clause is implemented internally as a compound SELECT. Hence, this option also disables the ability to insert more than a single row using an INSERT INTO ... VALUES ... statement. } COMPILE_OPTION {SQLITE_OMIT_DATETIME_FUNCS} { If this option is defined, SQLite's built-in date and time manipulation functions are omitted. Specifically, the SQL functions julianday(), date(), time(), datetime() and strftime() are not available. The default column values CURRENT_TIME, CURRENT_DATE and CURRENT_TIMESTAMP are still available. } | > > > > > > | 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 | cause a parse error. An [INSERT] statement with multiple values in the VALUES clause is implemented internally as a compound SELECT. Hence, this option also disables the ability to insert more than a single row using an INSERT INTO ... VALUES ... statement. } COMPILE_OPTION {SQLITE_OMIT_CTE} { This option causes support for [common table expressions] to be omitted. } COMPILE_OPTION {SQLITE_OMIT_DATETIME_FUNCS} { If this option is defined, SQLite's built-in date and time manipulation functions are omitted. Specifically, the SQL functions julianday(), date(), time(), datetime() and strftime() are not available. The default column values CURRENT_TIME, CURRENT_DATE and CURRENT_TIMESTAMP are still available. } |
︙ | ︙ |
Changes to pages/famous.in.
︙ | ︙ | |||
198 199 200 201 202 203 204 | of SQLite in the Skype client for Mac OS X and Windows. </td></tr> <tr><td valign="top"> <a href="http://www.tcl.tk/"> <img src="images/foreignlogos/tcl.gif" border="0"></a> </td><td> | | | 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 | of SQLite in the Skype client for Mac OS X and Windows. </td></tr> <tr><td valign="top"> <a href="http://www.tcl.tk/"> <img src="images/foreignlogos/tcl.gif" border="0"></a> </td><td> The Tcl/Tk programming language now comes with SQLite built-in. SQLite works particularly well with Tcl since SQLite was originally a Tcl extension that subsequently "escaped" into the wild. </td> <tr><td valign="top"> <a href="http://www.toshiba.com/"> <img src="images/foreignlogos/toshiba.gif" border="0"></a> |
︙ | ︙ |
Changes to pages/fileformat2.in.
︙ | ︙ | |||
1390 1391 1392 1393 1394 1395 1396 | The sqlite_stat4.nEq column holds a list of integers where the K-th integer is the approximate number of entries in the index whose left-most K columns exactly match the K left-most columns of the sample. The sqlite_stat4.nLt holds a list of integers where the K-th integer is the approximate number of entries in the index whose K left-most columns are collectively less than the K left-most columns of the sample. | | | 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 | The sqlite_stat4.nEq column holds a list of integers where the K-th integer is the approximate number of entries in the index whose left-most K columns exactly match the K left-most columns of the sample. The sqlite_stat4.nLt holds a list of integers where the K-th integer is the approximate number of entries in the index whose K left-most columns are collectively less than the K left-most columns of the sample. The sqlite_stat4.nDLt column holds a list of integers where the K-th integers is the approximate number of entries in the index that are distinct in the first K columns and that are whose left-most K columns are collectively less than the left-most K columns of the sample. <p>The sqlite_stat4 is a generalization of the sqlite_stat3 table. The sqlite_stat3 table provides information about the left-most column of an |
︙ | ︙ |
Changes to pages/fts3.in.
︙ | ︙ | |||
1877 1878 1879 1880 1881 1882 1883 | "integrity-check" command silently succeeds if the inverted indices are all ok, but will fail with an SQLITE_CORRUPT error if any problems are found. <p> The "integrity-check" command is similar in concept to [PRAGMA integrity_check]. In a working system, the "integrity-command" | | | 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 | "integrity-check" command silently succeeds if the inverted indices are all ok, but will fail with an SQLITE_CORRUPT error if any problems are found. <p> The "integrity-check" command is similar in concept to [PRAGMA integrity_check]. In a working system, the "integrity-command" should always be successful. Possible causes of integrity-check failures include: <ul> <li> The application has made changes to the [FTS shadow tables] directly, without using the FTS3/4 virtual table, causing the shadow tables to become out of sync with each other. <li> Using the [FTS4 content option] and failing to manually keep the content in sync with the FTS4 inverted indices. |
︙ | ︙ |
Changes to pages/lang.in.
︙ | ︙ | |||
3429 3430 3431 3432 3433 3434 3435 | ......Gail </pre></blockquote> <p>When the ORDER BY clause is omitted from the recursive-select, the queue behaves as a FIFO, which results in a breadth-first search. | | | 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 | ......Gail </pre></blockquote> <p>When the ORDER BY clause is omitted from the recursive-select, the queue behaves as a FIFO, which results in a breadth-first search. <tcl>hd_fragment mandelbrot {compute the Mandelbrot set}</tcl> <h4>Outlandish Recursive Query Examples</h4> <p>The following query computes an approximation of the Mandelbrot Set and outputs the result as ASCII-art: <blockquote><pre> WITH RECURSIVE |
︙ | ︙ | |||
3496 3497 3498 3499 3500 3501 3502 | .......+####.... + ..+####+. ..#*.. ....# +. </pre></blockquote> | | | 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 | .......+####.... + ..+####+. ..#*.. ....# +. </pre></blockquote> <tcl>hd_fragment sudoku {solve Sudoku puzzles} </tcl> <p>This next query solves a Sudoku puzzle. The state of the puzzle is defined by an 81-character string formed by reading entries from the puzzle box row by row from left to right and then from top to bottom. Blank squares in the puzzle are denoted by a "." character. Thus the input string: <blockquote> |
︙ | ︙ |
Changes to pages/news.in.
︙ | ︙ | |||
14 15 16 17 18 19 20 21 22 23 24 25 26 27 | 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 {2013-12-06} {Release 3.8.2} { <p>SQLite [version 3.8.2] is a regularly scheduled maintenance release. Upgrading from the previous release is optional. <p>Version 3.8.2 adds support for [WITHOUT ROWID] tables. This is a significant extension to SQLite. Database files that contain WITHOUT ROWID | > > > > > > > > > > > > > > > > > > | 14 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 | 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 {2014-02-03} {Release 3.8.3} { <p>SQLite [version 3.8.3] is a regularly scheduled maintenance release. Upgrading from the previous release is optional. <p>The most visible change in version 3.8.3 is the addition of support for [common table expressions]. It is now possible to write a single [SELECT] statement that will query a tree or graph, using either a depth-first or a breadth-first search. A single SQLite query will even [solve Sudoku puzzles] or [compute the Mandelbrot set]. As part of this change, SQLite now accepts a [VALUES clause] anyplace that a [SELECT] statement is valid. <p>This release also includes many small performance enhancements which should give a small speed boost to legacy applications. And there are other minor enhancements such as the addition of the [printf()] SQL function. See the [version 3.8.3|change log] for details. } newsitem {2013-12-06} {Release 3.8.2} { <p>SQLite [version 3.8.2] is a regularly scheduled maintenance release. Upgrading from the previous release is optional. <p>Version 3.8.2 adds support for [WITHOUT ROWID] tables. This is a significant extension to SQLite. Database files that contain WITHOUT ROWID |
︙ | ︙ | |||
198 199 200 201 202 203 204 | 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]. } | < < < < < < < | < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < | 216 217 218 219 220 221 222 223 224 225 226 | 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]. } </tcl> <a href="oldnews.html">Old news...</a> |
Changes to pages/oldnews.in.
1 2 3 4 5 6 7 8 9 10 11 12 13 | <?xml version="1.0" encoding="Windows-1252"?> <title>SQLite Older News</title> <tcl> proc newsitem {date title text} { regsub -all {[^a-z0-9]} $date _ tag hd_puts "<a name=\"$tag\"></a>" hd_puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt hd_resolve "<blockquote>$txt</blockquote>" hd_puts "<hr width=\"50%\">" } | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 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 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 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 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 | <?xml version="1.0" encoding="Windows-1252"?> <title>SQLite Older News</title> <tcl> proc newsitem {date title text} { regsub -all {[^a-z0-9]} $date _ tag hd_puts "<a name=\"$tag\"></a>" hd_puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt hd_resolve "<blockquote>$txt</blockquote>" hd_puts "<hr width=\"50%\">" } 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 a [CHECK constraint] or within a [view]. Collating functions are associated with individual database connections. But a pointer to the collating function was also being cached within expressions. If an expression was part of the schema and contained a cached collating function, it would point to the collating function in the database connection that originally parsed the schema. If that database connection closed while other database connections using the same shared cache continued to operate, they other database connections would try to use the deallocated collating function in the database connection that closed. The fix in version 3.7.15 was to not cache collating function pointers in the expression structure but instead look them up each time a new statement is prepared. This release also contains some important enhancements to the query planner which should (we hope) make some queries run faster. The enhancements include: <ol><li><p>When doing a full-table scan, try to use an index instead of the original table, under the theory that indices contain less information and are thus smaller and hence require less disk I/O to scan.</p> <li><p>Enhance the [IN operator] to allow it to make use of indices that have [affinity | numeric affinity].</p> <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 to simply remove the OS/2 code from the SQLite tree. If there are OS/2 projects out there that still need SQLite support, they can continue to maintain their own private [VFS] which can be linked to SQLite at start-time using the [sqlite3_vfs_register()] interface. The [sqlite3_close_v2()] interface has been added. The sqlite3_close_v2() interface differs from sqlite3_close() in that it is designed to work better for host language that use a garbage collector. With the older sqlite3_close() interface, the associated [prepared statements] and [sqlite3_backup] objects must be destroyed before the database connection. With the newer sqlite3_close_v2() interface, the objects can be destroyed in any order. 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 filenames should be full pathnames. Note that SQLite is not capable of accessing databases outside the installation directory and application data directory. This restriction is another security and safety feature of WinRT. Apart from these restrictions, SQLite should work exactly the same on WinRT as it does on every other system. Also in this release: when a database is opened using [URI filenames] and the [coreqp | mode=memory] query parameter then the database is an in-memory database, just as if it had been named ":memory:". But, if shared cache mode is enabled, then all other database connections that specify the same URI filename will connect to the same in-memory database. This allows two or more database connections (in the same process) to share the same in-memory database. This release also includes some corner-case performance optimizations that are obscure yet significant to an important subset of SQLite users. 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. } newsitem {2012-03-20} {Version 3.7.11} { SQLite [version 3.7.11] is a regularly scheduled maintenance release which was rushed out early due to a [http://www.sqlite.org/src/info/b7c8682cc1 | bug in the query optimizer] introduced in the previous release. The bug is obscure - it changes a LEFT JOIN into an INNER JOIN in some cases when there is a 3-way join and OR terms in the WHERE clause. But it was considered serious enough to rush out a fix. Apart from this one problem, SQLite [version 3.7.10] has not given any trouble. Upgrading to [version 3.7.11] from versions 3.7.6.3, 3.7.7, 3.7.7.1, 3.7.8, or 3.7.9 is optional. Upgrading from other releases, including the previous release 3.7.10, is recommended. Other enhancements found in this release are enumerated in the [version 3.7.11 | change log]. } newsitem {2012-01-16} {Version 3.7.10} { SQLite [version 3.7.10] is a regularly scheduled maintenance release. Upgrading from version 3.7.6.3, 3.7.7, 3.7.7.1, 3.7.8, or 3.7.9 is optional. Upgrading from other releases is recommended. The [SQLITE_CONFIG_PCACHE] mechanism has been replaced with [SQLITE_CONFIG_PCACHE2]. If you do not know what this mechanism is (it is an extreme corner-case and is seldom used) then this |
︙ | ︙ | |||
75 76 77 78 79 80 81 | could in theory result in a corrupt database file if a power loss occurred at just the wrong moment on an unusually cantankerous disk drive. But that is mostly a theoretical concern and is very unlikely to happen in practice. The bug was found during laboratory testing and has never been observed to occur in the wild. } | | | 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 | could in theory result in a corrupt database file if a power loss occurred at just the wrong moment on an unusually cantankerous disk drive. But that is mostly a theoretical concern and is very unlikely to happen in practice. The bug was found during laboratory testing and has never been observed to occur in the wild. } newsitem {2011-11-01} {Version 3.7.9} { SQLite [version 3.7.9] is a regularly scheduled maintenance release. Upgrading from version 3.7.6.3, 3.7.7, 3.7.7.1, and 3.7.8 is optional. Upgrading from other versions is recommended. The [SQLITE_ENABLE_STAT2] compile-time option is now a no-op. The enhanced query-planner functionality formerly available using SQLITE_ENABLE_STAT2 is now available through [SQLITE_ENABLE_STAT3]. The enhanced query planning |
︙ | ︙ | |||
136 137 138 139 140 141 142 | Every version of SQLite is better tested than the previous, and 3.7.8 is no exception to this rule. Version 3.7.8 has been used internally by the SQLite team for mission critical functions and has performed flawlessly. And, of course, it passes our rigorous [testing] procedures with no problems detected. Version 3.7.8 is recommended for all new development. } | | | | 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 | Every version of SQLite is better tested than the previous, and 3.7.8 is no exception to this rule. Version 3.7.8 has been used internally by the SQLite team for mission critical functions and has performed flawlessly. And, of course, it passes our rigorous [testing] procedures with no problems detected. Version 3.7.8 is recommended for all new development. } newsitem {2011-06-28} {Version 3.7.7.1} { SQLite [version 3.7.7.1] adds a one-line bug fix to 3.7.7 to fix [http://www.sqlite.org/src/info/25ee812710 | a problem] causing [PRAGMA case_sensitive_like] statements compiled using the legacy [sqlite3_prepare()] interface to fail with an [SQLITE_SCHEMA] error. Because [sqlite3_exec()] uses sqlite3_prepare() internally, the problem also affects sqlite3_exec(). Upgrading from 3.7.7 is only required for applications that use "PRAGMA case_sensitive_like" and the sqlite3_prepare() (or sqlite3_exec()) interface. } newsitem {2011-06-24} {Version 3.7.7} { SQLite [version 3.7.7] is a regularly scheduled bi-monthly maintenance release. Upgrading from version 3.7.6.3 is optional. Upgrading from all prior releases is recommended. This release adds support for naming database files using [URI filenames]. URI filenames are disabled by default (for backwards compatibility) but applications are encouraged to enable them since incompatibilities are |
︙ | ︙ | |||
186 187 188 189 190 191 192 | There has been a fair amount of work done on the FTS4 module for this release. But the core SQLite code has changed little and the previous release has not given any problems, so we expect this to be a very stable release. } | | | 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 | There has been a fair amount of work done on the FTS4 module for this release. But the core SQLite code has changed little and the previous release has not given any problems, so we expect this to be a very stable release. } newsitem {2011-05-19} {Version 3.7.6.3} { SQLite [version 3.7.6.3] is a patch release that fixes a [http://www.sqlite.org/src/info/2d1a5c67df | single bug] associated with [WAL mode]. The bug has been in SQLite ever since WAL was added, but the problem is very obscure and so nobody has noticed before now. Nevertheless, all users are encouraged to upgrade to version 3.7.6.3 or later. |
︙ | ︙ | |||
232 233 234 235 236 237 238 | The fix to this problem was that if all changed pages has already been written to the WAL when the commit was started, then page 1 of the database will be written to the WAL again, so that there will always be a page available on which to set the commit flag. } | | | | | | 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 | The fix to this problem was that if all changed pages has already been written to the WAL when the commit was started, then page 1 of the database will be written to the WAL again, so that there will always be a page available on which to set the commit flag. } newsitem {2011-04-17} {Version 3.7.6.2} { SQLite [version 3.7.6.2] adds a one-line bug fix to 3.7.6.1 that enables pthreads to work correctly on NetBSD. The problem was a faulty function signature for the open system call. The problem does not appear to have any adverse impact on any system other than NetBSD. Upgrading from version 3.7.6.1 is only needed on NetBSD. } newsitem {2011-04-13} {Version 3.7.6.1} { SQLite [version 3.7.6.1] fixes a single bug in 3.7.6 that can cause a segfault if [SQLITE_FCNTL_SIZE_HINT] is used on a unix build that has SQLITE_ENABLE_LOCKING_MODE set to 0 and is compiled with HAVE_POSIX_FALLOCATE. Upgrading from 3.7.6 is only needed for users effected by the configuration-specific bug described above. There are no other changes to the code. } newsitem {2011-04-12} {Version 3.7.6} { SQLite [version 3.7.6] is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from version 3.7.5 is optional. Upgrading releases prior to 3.7.5 is recommended. } newsitem {2011-02-01} {Version 3.7.5} { SQLite [version 3.7.5] is a regularly scheduled bi-monthly maintenance release of SQLite. Due to the discovery and fix of [http://www.sqlite.org/src/tktview?name=5d863f876e | an obscure bug] that could cause database corruption, upgrading from all prior releases of SQLite is recommended. This bug was found during code review and has not been observed in the wild. |
︙ | ︙ | |||
289 290 291 292 293 294 295 | is now available on [http://System.Data.SQLite.org/]. The originator of System.Data.SQLite, Robert Simpson, is aware of this fork, has expressed his approval, and has commit privileges on the new Fossil repository. The SQLite development team intends to maintain System.Data.SQLite moving forward. } | | | 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 | is now available on [http://System.Data.SQLite.org/]. The originator of System.Data.SQLite, Robert Simpson, is aware of this fork, has expressed his approval, and has commit privileges on the new Fossil repository. The SQLite development team intends to maintain System.Data.SQLite moving forward. } newsitem {2010-12-08} {Version 3.7.4} { SQLite [version 3.7.4] is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from [version 3.7.2] and [version 3.7.3] is optional. Upgrading from all other SQLite releases is recommended. This release features [full-text search] enhancements. The older [FTS3] virtual table is still fully supported, and should also run faster. In addition, the new [FTS4] virtual table is added. FTS4 |
︙ | ︙ | |||
405 406 407 408 409 410 411 | SQLite [version 3.7.0.1] is a patch release to fix a bug in the new filesize-in-header feature of the [file format | SQLite file format] that could cause database corruption if the same database file is written alternately with version 3.7.0 and version 3.6.23.1 or earlier. A performance regression was also fixed in this release. } | | | | | 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 | SQLite [version 3.7.0.1] is a patch release to fix a bug in the new filesize-in-header feature of the [file format | SQLite file format] that could cause database corruption if the same database file is written alternately with version 3.7.0 and version 3.6.23.1 or earlier. A performance regression was also fixed in this release. } newsitem {2010-07-22} {Version 3.7.0} { SQLite [version 3.7.0] is a major release of SQLite that features a new transaction control mechanism using a [write-ahead log] or [WAL]. The traditional rollback-journal is still used as the default so there should be no visible change for legacy programs. But newer programs can take advantage of improved performance and concurrency by enabling the WAL journaling mode. SQLite version 3.7.0 also contains some query planner enhancements and a few obscure bug fixes, but the only really big change is the addition of WAL mode. } newsitem {2010-03-30} {Version 3.6.23.1} { SQLite [version 3.6.23.1] is a patch release to fix a bug in the offsets() function of [FTS3] at the request of the Mozilla. } newsitem {2010-03-09} {Version 3.6.23} { SQLite [version 3.6.23] is a regular bimonthly release of SQLite. Upgrading from the prior release is purely optional. This release contains new pragmas: the [secure_delete pragma], and the [compile_options pragma]. There are a new SQL functions: [sqlite_compileoption_used()] and [sqlite_compileoption_get()]. |
︙ | ︙ | |||
445 446 447 448 449 450 451 | The ".genfkey" command in the [Command Line Interface] has been removed. SQLite has supported standard SQL [foreign key constraints] since [version 3.6.19] and so the ".genfkey" command was seen as an anachronism. } | | | 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 | The ".genfkey" command in the [Command Line Interface] has been removed. SQLite has supported standard SQL [foreign key constraints] since [version 3.6.19] and so the ".genfkey" command was seen as an anachronism. } newsitem {2010-01-06} {Version 3.6.22} { SQLite [version 3.6.22] is a bug-fix release. Two bugs have been fixed that might cause incorrect query results. <ul> <li>Ticket [http://www.sqlite.org/src/info/31338dca7e | 31338dca7e] describes a problem with queries that have a WHERE clause of the form (x AND y) OR z where x and z come from one table of a join and y comes from a different |
︙ | ︙ | |||
469 470 471 472 473 474 475 | recommended that all applications upgrade SQLite to version 3.6.22. This release also includes other minor bug fixes and performance enhancements, especially in the [FTS3] extension. } | | | | | | 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 | recommended that all applications upgrade SQLite to version 3.6.22. This release also includes other minor bug fixes and performance enhancements, especially in the [FTS3] extension. } newsitem {2009-12-07} {Version 3.6.21} { SQLite [version 3.6.21] focuses on performance optimization. For a certain set of traces, this version uses 12% fewer CPU instructions than the previous release (as measured by Valgrind). In addition, the [FTS3] extension has been through an extensive cleanup and rework and the [sqlite3_trace()] interface has been modified to insert [bound parameter] values into its output. } newsitem {2009-11-04} {Version 3.6.20} { SQLite [version 3.6.20] is a general maintenance release. The query planner has been enhanced to work better with bound parameters in LIKE and GLOB operators and in range constraints and various minor bugs have been fixed. Upgrading from 3.6.19 is optional. } newsitem {2009-10-14} {Version 3.6.19} { SQLite [version 3.6.19] adds native support for [foreign key constraints], including deferred constraints and cascading deletes. Enforcement of foreign keys is disabled by default for backwards compatibility and must be turned on using the [foreign_keys pragma]. Version 3.6.19 also adds support for the [IS operator | IS and IS NOT operators]. Formerly, SQLite (as most other SQL database engines) supported IS NULL and IS NOT NULL. The IS and IS NOT operators are generalizations that allow the right-hand side to be an arbitrary expression. IS and IS NOT work the same as == (equals) and != (not equals) except that with IS and IS NOT the NULL values compare equal to one another. } newsitem {2009-09-11} {Version 3.6.18} { Beginning with this release, the SQLite source code is tracked and managed using the [http://www.fossil-scm.org/ | Fossil] distributed configuration management system. SQLite was previously versioned using CVS. The entire CVS history has been imported into Fossil. The older CVS repository remains on the website but is read-only. |
︙ | ︙ | |||
542 543 544 545 546 547 548 | The SQLite core continues to have [test coverage | 100% branch test coverage] and so despite the many changes in this release, the developers believe that this version of SQLite is stable and ready for production use. } | | | | | | | | | 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 | The SQLite core continues to have [test coverage | 100% branch test coverage] and so despite the many changes in this release, the developers believe that this version of SQLite is stable and ready for production use. } newsitem {2009-08-10} {Version 3.6.17} { This is a monthly maintenance release with a focus of bug fixes, performance improvements, and increased test coverage. This is the first release of SQLite since [test coverage | 100% branch test coverage] was achieved on the SQLite core. In addition, a new interface [sqlite3_strnicmp()] is provided for the convenience of extension writers. None of the bugs fixed in this release are serious. All bugs are obscure. Upgrading is optional. } newsitem {2009-07-25} {100% Branch Test Coverage} { A subset of the [TH3] test suite was measured by gcov to provide [test coverage | 100% branch test coverage] over the SQLite core (exclusive of the VFS backend and of extensions such as FTS3 and RTREE) when compiled for SuSE 10.1 Linux on x86. The SQLite developers pledge to maintain branch test coverage at 100% in all future releases. Ongoing work will strive for 100% branch test coverage on the operating-system backends and extensions as well. } newsitem {2009-06-27} {Version 3.6.16} { SQLite [version 3.6.16] is another general maintenance release containing performance and robustness enhancements. A single notable bug was fixed (ticket #3929). This bug cause cause INSERT or UPDATE statements to fail on indexed tables that have AFTER triggers that modify the same table and index. } newsitem {2009-06-15} {Version 3.6.15} { SQLite [version 3.6.15] is a general maintenance release containing performance and robustness enhancements and fixes for various obscure bugs. } newsitem {2009-05-25} {Version 3.6.14.2} { SQLite [version 3.6.14.2] fixes an obscure bug in the code generator (<a href="http://www.sqlite.org/cvstrac/tktview?tn=3879">ticket #3879</a>) section of SQLite which can potentially cause incorrect query results. The changes from the prior release consist of only this one bug fix, check-in <a href="http://www.sqlite.org/cvstrac/chngview?cn=6676">[6676]</a> and a change to the version number text. The bug was introduced in version 3.6.14. It is recommended that users of version 3.6.14 and 3.6.14.1 upgrade to this release. Applications are unlikely to hit this bug, but since it is difficult to predict which applications might hit it and which might not, we recommend that all users of 3.6.14 and 3.5.14.1 upgrade to this release. } newsitem {2009-05-19} {Version 3.6.14.1} { SQLite [version 3.6.14.1] is a patch release to [version 3.6.14] with minimal changes that fixes three bugs. Upgrading is only necessary for users who are impacted by one or more of those bugs. } newsitem {2009-05-07} {Version 3.6.14} { SQLite [version 3.6.14] provides new performance enhancements in the btree and pager layers and in the query optimizer. Certain workloads can be as much as twice as fast as the previous release, though 10% faster is a more typical result. Queries against [virtual tables] that contain OR and IN operators in the WHERE clause are now able to use indexing. |
︙ | ︙ | |||
625 626 627 628 629 630 631 | new test cases, and cleanups and simplifications to the source code. There is no compelling reason to upgrade from versions 3.6.12 or 3.6.13 if those prior versions are working. Though many users may benefit from the improved performance. } | | | | | | | | | | | | | | | | | | | | | | | | | | | 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 | new test cases, and cleanups and simplifications to the source code. There is no compelling reason to upgrade from versions 3.6.12 or 3.6.13 if those prior versions are working. Though many users may benefit from the improved performance. } newsitem {2008-12-16} {Version 3.6.7} { SQLite [version 3.6.7] contains a major cleanup of the Unix driver, and support for the new Proxy Locking mechanism on Mac OS X. Though the Unix driver is reorganized, its functionality is the same and so applications should not notice a difference. } newsitem {2008-11-26} {Version 3.6.6.2} { This release fixes a bug that was introduced into SQLite [version 3.6.6] and which seems like it might be able to cause database corruption. This bug was detected during stress testing. It has not been seen in the wild. An analysis of the problem suggests that the bug might be able to cause database corruption, however focused efforts to find a real-world test cases that actually causes database corruption have so far been unsuccessful. Hence, the likelihood of this bug causing problems is low. Nevertheless, we have decided to do an emergency branch release out of an abundance of caution. The [version 3.6.6.2] release also fixes an obscure memory leak that can occur following a disk I/O error. } newsitem {2008-11-22} {Version 3.6.6.1} { This release fixes a bug that was introduced into SQLite [version 3.6.4] and that can cause database corruption in obscure cases. This bug has never been seen in the wild; it was first detected by internal stress tests and required substantial analysis before it could be shown to potentially lead to corruption. So we feel that SQLite versions 3.6.4, 3.6.5, and 3.6.6 are safe to use for development work. But upgrading to this patch release or later is recommended prior to deploying products that incorporate SQLite. We have taken the unusual step of issuing a patch release in order to get the fix for this bug into circulation quickly. SQLite version 3.6.7 will continue on its normal path of development with an anticipated release in mid December. } newsitem {2008-11-19} {Version 3.6.6} { SQLite [version 3.6.5] is released. This is a quick turn-around release that fixes a bug in virtual tables and FTS3 that snuck into [version 3.6.5]. This release also adds the new application-defined page cache mechanism. } newsitem {2008-11-12} {Version 3.6.5} { SQLite [version 3.6.5] is released. There are various minor feature enhancements and numerous obscure bug fixes. The [version 3.6.5|change log] contains the details. Upgrading is optional. } newsitem {2008-11-01} {Bloomberg Joins SQLite Consortium} { The SQLite developers are honored to announce that [http://www.bloomberg.com/ | Bloomberg] has joined the [SQLite Consortium]. } newsitem {2008-10-15} {Version 3.6.4} { SQLite version 3.6.4 adds new features designed to help applications detect when indices are not being used on query. There are also some important performance improvements. Upgrading is optional. } newsitem {2008-09-22} {Version 3.6.3} { SQLite version 3.6.3 fixes a bug in SELECT DISTINCT that was introduced by the previous version. No new features are added. Upgrading is recommended for all applications that make use of DISTINCT. } newsitem {2008-08-30} {Version 3.6.2} { SQLite version 3.6.2 contains rewrites of the page-cache subsystem and the procedures for matching identifiers to table columns in SQL statements. These changes are designed to better modularize the code and make it more maintainable and reliable moving forward. Nearly 5000 non-comment lines of core code (about 11.3%) have changed from the previous release. Nevertheless, there should be no application-visible changes, other than bug fixes. } newsitem {2008-08-06} {Version 3.6.1} { SQLite version 3.6.1 is a stabilization and performance enhancement release. } newsitem {2008-07-16} {Version 3.6.0 beta} { Version 3.6.0 makes changes to the [sqlite3_vfs | VFS] object in order to make SQLite more easily portable to a wider variety of platforms. There are potential incompatibilities with some legacy applications. See the [35to36 | 35to36.html] document for details. Many new interfaces are introduced in version 3.6.0. The code is very well tested and is appropriate for use in stable systems. We have attached the "beta" designation only so that we can make tweaks to the new interfaces in the next release without having to declare an incompatibility. } newsitem {2008-05-12} {Version 3.5.9} { Version 3.5.9 adds a new experimental [PRAGMA]: [journal_mode]. Setting the journal mode to PERSIST can provide performance improvement on systems where deleting a file is expensive. The PERSIST journal mode is still considered experimental and should be used with caution pending further testing. Version 3.5.9 is intended to be the last stable release prior to version 3.6.0. Version 3.6.0 will make incompatible changes to the [sqlite3_vfs] VFS layer in order to address deficiencies in the original design. These incompatibilities will only effect programmers who write their own custom VFS layers (typically embedded device builders). The planned VFS changes will be much smaller than the changes that occurred on the [34to35 | 3.4.2 to 3.5.0 transaction] that occurred last September. This release of SQLite is considered stable and ready for production use. } newsitem {2008-04-16} {Version 3.5.8} { Version 3.5.8 includes some important new performance optimizations in the virtual machine code generator, including constant subexpression factoring and common subexpression elimination. This release also creates new public interfaces: [sqlite3_randomness()] provides access to SQLite's internal pseudo-random number generator, [sqlite3_limit()] allows size limits to be set at run-time on a per-connection basis, and [sqlite3_context_db_handle()] is a convenience routine that allows an application-defined SQL function implementation to retrieve its [database connection] handle. This release of SQLite is considered stable and ready for production use. } newsitem {2008-03-17} {Version 3.5.7} { Version 3.5.7 fixes several minor and obscure bugs, especially in the autoconf-generated makefile. Upgrading is optional. This release of SQLite is considered stable and ready for production use. } newsitem {2008-02-06} {Version 3.5.6} { Version 3.5.6 fixes a minor regression in 3.5.5 - a regression that had nothing to do with the massive change of the virtual machine to a register-based design. No problems have been reported with the new virtual machine. This release of SQLite is considered stable and ready for production use. } newsitem {2008-01-31} {Version 3.5.5} { Version 3.5.5 changes over 8% of the core source code of SQLite in order to convert the internal virtual machine from a stack-based design into a register-based design. This change will allow future optimizations and will avoid an entire class of stack overflow bugs that have caused problems in the past. Even though this change is large, extensive testing has found zero errors in the new virtual machine and so we believe this to be a very stable release. } newsitem {2007-12-14} {Version 3.5.4} { Version 3.5.4 fixes a long-standing but obscure bug in UPDATE and DELETE which might cause database corruption. (See ticket #2832.) Upgrading is recommended for all users. This release also brings the processing of ORDER BY statements into compliance with standard SQL. This could, in theory, cause problems for existing applications that depend on the older, buggy behavior. See ticket #2822 for additional information. } newsitem {2007-12-12} {SQLite Consortium Announced} { The <a href="consortium.html">SQLite Consortium</a> was launched today with [http://www.mozilla.org/ | Mozilla] and [http://www.symbian.com/ | Symbian] as charter members. As noted in the <a href="pressrelease-20071212.html">press release</a>, the Consortium's goal is to promote the continuing vitality and independence of SQLite. } newsitem {2007-11-27} {Version 3.5.3} { This is an incremental release that fixes several minor problems. Upgrading is optional. If Version 3.5.2 or 3.5.1 is working fine for you, then there is no pressing need to change to 3.5.3. The prebuilt binaries and the amalgamation found on the <a href="download.html">download</a> page include the FTS3 fulltext search extension module. We are doing this on an experimental basis and are not promising to provide prebuilt binaries with FTS3 in the future. } newsitem {2007-11-05} {Version 3.5.2} { This is an incremental release that fixes several minor problems, adds some obscure features, and provides some performance tweaks. Upgrading is optional. The experimental compile-time option [omitfeatures | SQLITE_OMIT_MEMORY_ALLOCATION] is no longer supported. On the other hand, it is now possible to compile SQLite so that it uses a static array for all its dynamic memory allocation needs and never calls malloc. Expect to see additional radical changes to the memory allocation subsystem in future releases. } newsitem {2007-10-04} {Version 3.5.1} { Fix a long-standing bug that might cause database corruption if a disk-full error occurs in the middle of a transaction and that transaction is not rolled back. <a href="http://www.sqlite.org/cvstrac/tktview?tn=2686">Ticket #2686.</a> The new VFS layer is stable. However, we still reserve the right to make tweaks to the interface definition of the VFS if necessary. } newsitem {2007-09-04} {Version 3.5.0 alpha} { The OS interface layer and the memory allocation subsystems in SQLite have been reimplemented. The published API is largely unchanged but the (unpublished) OS interface has been modified extensively. Applications that implement their own OS interface will require modification. See <a href="34to35.html">34to35.html</a> for details.<p> This is a large change. Approximately 10% of the source code was modified. We are calling this first release "alpha" in order to give the user community time to test and evaluate the changes before we freeze the new design. } newsitem {2007-08-13} {Version 3.4.2} { While stress-testing the <a href="c3ref/soft_heap_limit.html">soft_heap_limit</a> feature, a bug that could lead to <a href="http://www.sqlite.org/cvstrac/wiki?p=DatabaseCorruption">database corruption</a> was <a href="http://www.sqlite.org/cvstrac/tktview?tn=2565"> discovered and fixed</a>. Though the consequences of this bug are severe, the chances of hitting it in a typical application are remote. Upgrading is recommended only if you use the <a href="c3ref/soft_heap_limit.html">sqlite3_soft_heap_limit</a> interface. } newsitem {2007-07-20} {Version 3.4.1} { This release fixes a bug in <a href="lang_vacuum.html">VACUUM</a> that can lead to <a href="http://www.sqlite.org/cvstrac/wiki?p=DatabaseCorruption"> database corruption</a>. The bug was introduced in version <a href="changes.html#version_3_3_14">3.3.14</a>. Upgrading is recommended for all users. Also included are a slew of other more routine <a href="changes.html#version_3_4_1">enhancements and bug fixes</a>. } newsitem {2007-06-18} {Version 3.4.0} { This release fixes two separate bugs either of which can lead to database corruption. Upgrading is strongly recommended. If you must continue using an older version of SQLite, please at least read about how to avoid these bugs at <a href="http://www.sqlite.org/cvstrac/wiki?p=CorruptionFollowingBusyError"> CorruptionFollowingBusyError</a> and |
︙ | ︙ | |||
901 902 903 904 905 906 907 | There are also new features, including <a href="c3ref/blob_open.html">incremental BLOB I/O</a> and <a href="pragma.html#pragma_incremental_vacuum">incremental vacuum</a>. See the <a href="changes.html#version_3_4_0">change log</a> for additional information. } | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 | There are also new features, including <a href="c3ref/blob_open.html">incremental BLOB I/O</a> and <a href="pragma.html#pragma_incremental_vacuum">incremental vacuum</a>. See the <a href="changes.html#version_3_4_0">change log</a> for additional information. } newsitem {2007-04-25} {Version 3.3.17} { This version fixes a bug in the forwards-compatibility logic of SQLite that was causing a database to become unreadable when it should have been read-only. Upgrade from 3.3.16 only if you plan to deploy into a product that might need to be upgraded in the future. For day to day use, it probably does not matter. } newsitem {2007-04-18} {Version 3.3.16} { Performance improvements added in 3.3.14 but mistakenly turned off in 3.3.15 have been reinstated. A bug has been fixed that prevented VACUUM from running if a NULL value was in a UNIQUE column. } newsitem {2007-04-09} {Version 3.3.15} { An annoying bug introduced in 3.3.14 has been fixed. There are also many enhancements to the test suite. } newsitem {2007-04-02} {Version 3.3.14} { This version focuses on performance improvements. If you recompile <a href="http://www.sqlite.org/cvstrac/wiki?p=TheAmalgamation"> the amalgamation</a> using GCC option -O3 (the precompiled binaries use -O2) you may see performance improvements of 35% or more over version 3.3.13 depending on your workload. This version also adds support for <a href="pragma.html#pragma_locking_mode"> exclusive access mode</a>. } newsitem {2007-02-13} {Version 3.3.13} { This version fixes a subtle bug in the ORDER BY optimizer that can occur when using joins. There are also a few minor enhancements. Upgrading is recommended. } newsitem {2007-01-27} {Version 3.3.12} { The first published build of the previous version used the wrong set of source files. Consequently, many people downloaded a build that was labeled as "3.3.11" but was really 3.3.10. Version 3.3.12 is released to clear up the ambiguity. A couple more bugs have also been fixed and <a href="pragma.html#pragma_integrity_check"> PRAGMA integrity_check</a> has been enhanced. } newsitem {2007-01-22} {Version 3.3.11} { Version 3.3.11 fixes for a few more problems in version 3.3.9 that version 3.3.10 failed to catch. Upgrading is recommended. } newsitem {2007-01-09} {Version 3.3.10} { Version 3.3.10 fixes several bugs that were introduced by the previous release. Upgrading is recommended. } newsitem {2007-01-04} {Version 3.3.9} { Version 3.3.9 fixes bugs that can lead to database corruption under obscure and difficult to reproduce circumstances. See <a href="http://www.sqlite.org/cvstrac/wiki?p=DatabaseCorruption"> DatabaseCorruption</a> in the <a href="http://www.sqlite.org/cvstrac/wiki">wiki</a> for details. This release also adds the new <a href="c3ref/prepare.html">sqlite3_prepare_v2()</a> API and includes important bug fixes in the command-line shell and enhancements to the query optimizer. Upgrading is recommended. } newsitem {2006-10-09} {Version 3.3.8} { Version 3.3.8 adds support for full-text search using the <a href="http://www.sqlite.org/cvstrac/wiki?p=FtsOne">FTS1 module.</a> There are also minor bug fixes. Upgrade only if you want to try out the new full-text search capabilities or if you are having problems with 3.3.7. } newsitem {2006-08-12} {Version 3.3.7} { Version 3.3.7 includes support for loadable extensions and virtual tables. But both features are still considered "beta" and their APIs are subject to change in a future release. This release is mostly to make available the minor bug fixes that have accumulated since 3.3.6. Upgrading is not necessary. Do so only if you encounter one of the obscure bugs that have been fixed or if you want to try out the new features. } newsitem {2006-06-19} {New Book About SQLite} { <i>[http://www.apress.com/book/bookDisplay.html?bID=10130 | The Definitive Guide to SQLite]</i>, a new book by [http://www.mikesclutter.com | Mike Owens] is now available from [http://www.apress.com | Apress]. The books covers the latest SQLite internals as well as the native C interface and bindings for PHP, Python, Perl, Ruby, Tcl, and Java. Recommended. } newsitem {2006-06-6} {Version 3.3.6} { Changes include improved tolerance for Windows virus scanners and faster :memory: databases. There are also fixes for several obscure bugs. Upgrade if you are having problems. } newsitem {2006-04-5} {Version 3.3.5} { This release fixes many minor bugs and documentation typos and provides some minor new features and performance enhancements. Upgrade only if you are having problems or need one of the new features. } newsitem {2006-02-11} {Version 3.3.4} { This release fixes several bugs, including a blunder that might cause a deadlock on multithreaded systems. Anyone using SQLite in a multithreaded environment should probably upgrade. } newsitem {2006-01-31} {Version 3.3.3 stable} { There have been no major problems discovered in version 3.3.2, so we hereby declare the new APIs and language features to be stable and supported. } newsitem {2006-01-24} {Version 3.3.2 beta} { More bug fixes and performance improvements as we move closer to a production-ready version 3.3.x. } newsitem {2006-01-16} {Version 3.3.1 alpha} { Many bugs found in last week's alpha release have now been fixed and the library is running much faster again. Database connections can now be moved between threads as long as the connection holds no locks at the time it is moved. Thus the common paradigm of maintaining a pool of database connections and handing them off to transient worker threads is now supported. Please help test this new feature. See <a href="http://www.sqlite.org/cvstrac/wiki?p=MultiThreading"> the MultiThreading wiki page</a> for additional information. } newsitem {2006-01-10} {Version 3.3.0 alpha} { Version 3.3.0 adds support for CHECK constraints, DESC indices, separate REAL and INTEGER column affinities, a new OS interface layer design, and many other changes. The code passed a regression test but should still be considered alpha. Please report any problems. The file format for version 3.3.0 has changed slightly to support descending indices and a more efficient encoding of boolean values. SQLite 3.3.0 will read and write legacy databases created with any prior version of SQLite 3. But databases created by version 3.3.0 will not be readable or writable by earlier versions of the SQLite. The older file format can be specified at compile-time for those rare cases where it is needed. } newsitem {2005-12-19} {Versions 3.2.8 and 2.8.17} { These versions contain one-line changes to 3.2.7 and 2.8.16 to fix a bug that has been present since March of 2002 and version 2.4.0. That bug might possibly cause database corruption if a large INSERT or UPDATE statement within a multi-statement transaction fails due to a uniqueness constraint but the containing transaction commits. } newsitem {2005-09-24} {Version 3.2.7} { This version fixes several minor and obscure bugs. Upgrade only if you are having problems. } newsitem {2005-09-16} {Version 3.2.6 - Critical Bug Fix} { This version fixes a bug that can result in database corruption if a VACUUM of a 1 gigabyte or larger database fails (perhaps do to running out of disk space or an unexpected power loss) and is later rolled back. <p> Also in this release: The ORDER BY and GROUP BY processing was rewritten to use less memory. Support for COUNT(DISTINCT) was added. The LIKE operator can now be used by the optimizer on columns with COLLATE NOCASE. } newsitem {2005-08-27} {Version 3.2.5} { This release fixes a few more lingering bugs in the new code. We expect that this release will be stable and ready for production use. } newsitem {2005-08-24} {Version 3.2.4} { This release fixes a bug in the new optimizer that can lead to segfaults when parsing very complex WHERE clauses. } newsitem {2005-08-21} {Version 3.2.3} { This release adds the <a href="lang_analyze.html">ANALYZE</a> command, the <a href="lang_expr.html">CAST</a> operator, and many very substantial improvements to the query optimizer. See the <a href="changes.html#version_3_2_3">change log</a> for additional information. } newsitem {2005-08-02} {2005 Open Source Award for SQLite} { SQLite and its primary author D. Richard Hipp have been honored with a [http://osdir.com/Article6677.phtml | 2005 Open Source Award] from Google and O'Reilly.<br clear="right"> } newsitem {2005-06-13} {Version 3.2.2} { This release includes numerous minor bug fixes, speed improvements, and code size reductions. There is no reason to upgrade unless you are having problems or unless you just want to. } newsitem {2005-03-29} {Version 3.2.1} { This release fixes a memory allocation problem in the new <a href="lang_altertable.html">ALTER TABLE ADD COLUMN</a> command. } newsitem {2005-03-21} {Version 3.2.0} { The primary purpose for version 3.2.0 is to add support for <a href="lang_altertable.html">ALTER TABLE ADD COLUMN</a>. The new ADD COLUMN capability is made possible by AOL developers supporting and embracing great open-source software. Thanks, AOL! Version 3.2.0 also fixes an obscure but serious bug that was discovered just prior to release. If you have a multi-statement transaction and within that transaction an UPDATE or INSERT statement fails due to a constraint, then you try to rollback the whole transaction, the rollback might not work correctly. See <a href="http://www.sqlite.org/cvstrac/tktview?tn=1171">Ticket #1171</a> for details. Upgrading is recommended for all users. } newsitem {2005-03-16} {Version 3.1.6} { Version 3.1.6 fixes a critical bug that can cause database corruption when inserting rows into tables with around 125 columns. This bug was introduced in version 3.0.0. See <a href="http://www.sqlite.org/cvstrac/tktview?tn=1163">Ticket #1163</a> for additional information. } newsitem {2005-03-11} {Versions 3.1.4 and 3.1.5 Released} { Version 3.1.4 fixes a critical bug that could cause database corruption if the autovacuum mode of version 3.1.0 is turned on (it is off by default) and a CREATE UNIQUE INDEX is executed within a transaction but fails because the indexed columns are not unique. Anyone using the autovacuum feature and unique indices should upgrade. Version 3.1.5 adds the ability to disable the F_FULLFSYNC ioctl() in OS-X by setting "PRAGMA synchronous=on" instead of the default "PRAGMA synchronous=full". There was an attempt to add this capability in 3.1.4 but it did not work due to a spelling error. } newsitem {2005-02-19} {Version 3.1.3 Released} { Version 3.1.3 cleans up some minor issues discovered in version 3.1.2. } newsitem {2005-02-15} {Versions 2.8.16 and 3.1.2 Released} { A critical bug in the VACUUM command that can lead to database corruption has been fixed in both the 2.x branch and the main 3.x line. This bug has existed in all prior versions of SQLite. Even though it is unlikely you will ever encounter this bug, it is suggested that all users upgrade. See <a href="http://www.sqlite.org/cvstrac/tktview?tn=1116"> ticket #1116</a>. for additional information. Version 3.1.2 is also the first stable release of the 3.1 series. SQLite 3.1 features added support for correlated subqueries, autovacuum, autoincrement, ALTER TABLE, and other enhancements. See the <a href="http://www.sqlite.org/releasenotes310.html">release notes for version 3.1.0</a> for a detailed description of the changes available in the 3.1 series. } newsitem {2005-02-01} {Version 3.1.1 (beta) Released} { Version 3.1.1 (beta) is now available on the website. Version 3.1.1 is fully backwards compatible with the 3.0 series and features many new features including Autovacuum and correlated subqueries. The <a href="http://www.sqlite.org/releasenotes310.html">release notes</a> From version 3.1.0 apply equally to this release beta. A stable release is expected within a couple of weeks. } newsitem {2005-01-21} {Version 3.1.0 (alpha) Released} { Version 3.1.0 (alpha) is now available on the website. Version 3.1.0 is fully backwards compatible with the 3.0 series and features many new features including Autovacuum and correlated subqueries. See the <a href="http://www.sqlite.org/releasenotes310.html">release notes</a> for details. This is an alpha release. A beta release is expected in about a week with the first stable release to follow after two more weeks. } newsitem {2004-11-09} {SQLite at the 2004 International PHP Conference} { There was a talk on the architecture of SQLite and how to optimize SQLite queries at the 2004 International PHP Conference in Frankfurt, Germany. <a href="http://www.sqlite.org/php2004/page-001.html"> Slides</a> from that talk are available. } newsitem {2004-10-11} {Version 3.0.8} { Version 3.0.8 of SQLite contains several code optimizations and minor bug fixes and adds support for DEFERRED, IMMEDIATE, and EXCLUSIVE transactions. This is an incremental release. There is no reason to upgrade from version 3.0.7 if that version is working for you. } newsitem {2004-10-10} {SQLite at the 11<sup><small>th</small></sup> Annual Tcl/Tk Conference} { There will be a talk on the use of SQLite in Tcl/Tk at the 11<sup><small>th</small></sup> Tcl/Tk Conference this week in New Orleans. Visit [http://www.tcl.tk/community/tcl2004/] for details. <a href="http://www.sqlite.org/tclconf2004/page-001.html"> Slides</a> from the talk are available. } newsitem {2004-09-18} {Version 3.0.7} { Version 3.0 has now been in use by multiple projects for several months with no major difficulties. We consider it stable and ready for production use. } newsitem {2004-09-02} {Version 3.0.6 (beta)} { Because of some important changes to sqlite3_step(), we have decided to do an additional beta release prior to the first "stable" release. If no serious problems are discovered in this version, we will release version 3.0 "stable" in about a week. } newsitem {2004-08-29} {Version 3.0.5 (beta)} { The fourth beta release of SQLite version 3.0 is now available. The next release is expected to be called "stable". } newsitem {2004-08-08} {Version 3.0.4 (beta)} { The third beta release of SQLite version 3.0 is now available. This new beta fixes several bugs including a database corruption problem that can occur when doing a DELETE while a SELECT is pending. Expect at least one more beta before version 3.0 goes final. } newsitem {2004-07-22} {Version 3.0.3 (beta)} { The second beta release of SQLite version 3.0 is now available. This new beta fixes many bugs and adds support for databases with varying page sizes. The next 3.0 release will probably be called a final or stable release. Version 3.0 adds support for internationalization and a new more compact file format. <a href="version3.html">Details.</a> The API and file format have been fixed since 3.0.2. All regression tests pass (over 100000 tests) and the test suite exercises over 95% of the code. SQLite version 3.0 is made possible in part by AOL developers supporting and embracing great Open-Source Software. } newsitem {2004-07-22} {Version 2.8.15} { SQLite version 2.8.15 is a maintenance release for the version 2.8 series. Version 2.8 continues to be maintained with bug fixes, but no new features will be added to version 2.8. All the changes in this release are minor. If you are not having problems, there is there is no reason to upgrade. } newsitem {2004-06-30} {Version 3.0.2 (beta) Released} { The first beta release of SQLite version 3.0 is now available. Version 3.0 adds support for internationalization and a new more compact file format. <a href="version3.html">Details.</a> As of this release, the API and file format are frozen. All regression tests pass (over 100000 tests) and the test suite exercises over 95% of the code. SQLite version 3.0 is made possible in part by AOL developers supporting and embracing great Open-Source Software. } newsitem {2004-06-25} {Website hacked} { The www.sqlite.org website was hacked sometime around 2004-06-22 because the lead SQLite developer failed to properly patch CVS. Evidence suggests that the attacker was unable to elevate privileges above user "cvs". Nevertheless, as a precaution the entire website has been reconstructed from scratch on a fresh machine. All services should be back to normal as of 2004-06-28. } newsitem {2004-06-18} {Version 3.0.0 (alpha) Released} { The first alpha release of SQLite version 3.0 is available for public review and comment. Version 3.0 enhances internationalization support through the use of UTF-16 and user-defined text collating sequences. BLOBs can now be stored directly, without encoding. A new file format results in databases that are 25% smaller (depending on content). The code is also a little faster. In spite of the many new features, the library footprint is still less than 240KB (x86, gcc -O1). <a href="version3.html">Additional information</a>. Our intent is to freeze the file format and API on 2004-07-01. Users are encouraged to review and evaluate this alpha release carefully and submit any feedback prior to that date. The 2.8 series of SQLite will continue to be supported with bug fixes for the foreseeable future. } newsitem {2004-06-09} {Version 2.8.14 Released} { SQLite version 2.8.14 is a patch release to the stable 2.8 series. There is no reason to upgrade if 2.8.13 is working ok for you. This is only a bug-fix release. Most development effort is going into version 3.0.0 which is due out soon. } newsitem {2004-05-31} {CVS Access Temporarily Disabled} { Anonymous access to the CVS repository will be suspended for 2 weeks beginning on 2004-06-04. Everyone will still be able to download prepackaged source bundles, create or modify trouble tickets, or view change logs during the CVS service interruption. Full open access to the CVS repository will be restored on 2004-06-18. } newsitem {2004-04-23} {Work Begins On SQLite Version 3} { Work has begun on version 3 of SQLite. Version 3 is a major changes to both the C-language API and the underlying file format that will enable SQLite to better support internationalization. The first beta is schedule for release on 2004-07-01. Plans are to continue to support SQLite version 2.8 with bug fixes. But all new development will occur in version 3.0. } </tcl> |