| 1 |
<!DOCTYPE html> |
| 2 |
<html><head> |
| 3 |
<meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| 4 |
<meta http-equiv="content-type" content="text/html; charset=UTF-8"> |
| 5 |
<link href="sqlite.css" rel="stylesheet"> |
| 6 |
<title>SQLite Older News</title> |
| 7 |
<!-- path= --> |
| 8 |
</head> |
| 9 |
<body> |
| 10 |
<div class=nosearch> |
| 11 |
<a href="index.html"> |
| 12 |
<img class="logo" src="images/sqlite370_banner.svg" alt="SQLite" border="0"> |
| 13 |
</a> |
| 14 |
<div><!-- IE hack to prevent disappearing logo --></div> |
| 15 |
<div class="tagline desktoponly"> |
| 16 |
Small. Fast. Reliable.<br>Choose any three. |
| 17 |
</div> |
| 18 |
<div class="menu mainmenu"> |
| 19 |
<ul> |
| 20 |
<li><a href="index.html">Home</a> |
| 21 |
<li class='mobileonly'><a href="javascript:void(0)" onclick='toggle_div("submenu")'>Menu</a> |
| 22 |
<li class='wideonly'><a href='about.html'>About</a> |
| 23 |
<li class='desktoponly'><a href="docs.html">Documentation</a> |
| 24 |
<li class='desktoponly'><a href="download.html">Download</a> |
| 25 |
<li class='wideonly'><a href='copyright.html'>License</a> |
| 26 |
<li class='desktoponly'><a href="support.html">Support</a> |
| 27 |
<li class='desktoponly'><a href="prosupport.html">Purchase</a> |
| 28 |
<li class='search' id='search_menubutton'> |
| 29 |
<a href="javascript:void(0)" onclick='toggle_search()'>Search</a> |
| 30 |
</ul> |
| 31 |
</div> |
| 32 |
<div class="menu submenu" id="submenu"> |
| 33 |
<ul> |
| 34 |
<li><a href='about.html'>About</a> |
| 35 |
<li><a href='docs.html'>Documentation</a> |
| 36 |
<li><a href='download.html'>Download</a> |
| 37 |
<li><a href='support.html'>Support</a> |
| 38 |
<li><a href='prosupport.html'>Purchase</a> |
| 39 |
</ul> |
| 40 |
</div> |
| 41 |
<div class="searchmenu" id="searchmenu"> |
| 42 |
<form method="GET" action="search"> |
| 43 |
<select name="s" id="searchtype"> |
| 44 |
<option value="d">Search Documentation</option> |
| 45 |
<option value="c">Search Changelog</option> |
| 46 |
</select> |
| 47 |
<input type="text" name="q" id="searchbox" value=""> |
| 48 |
<input type="submit" value="Go"> |
| 49 |
</form> |
| 50 |
</div> |
| 51 |
</div> |
| 52 |
<script> |
| 53 |
function toggle_div(nm) { |
| 54 |
var w = document.getElementById(nm); |
| 55 |
if( w.style.display=="block" ){ |
| 56 |
w.style.display = "none"; |
| 57 |
}else{ |
| 58 |
w.style.display = "block"; |
| 59 |
} |
| 60 |
} |
| 61 |
function toggle_search() { |
| 62 |
var w = document.getElementById("searchmenu"); |
| 63 |
if( w.style.display=="block" ){ |
| 64 |
w.style.display = "none"; |
| 65 |
} else { |
| 66 |
w.style.display = "block"; |
| 67 |
setTimeout(function(){ |
| 68 |
document.getElementById("searchbox").focus() |
| 69 |
}, 30); |
| 70 |
} |
| 71 |
} |
| 72 |
function div_off(nm){document.getElementById(nm).style.display="none";} |
| 73 |
window.onbeforeunload = function(e){div_off("submenu");} |
| 74 |
/* Disable the Search feature if we are not operating from CGI, since */ |
| 75 |
/* Search is accomplished using CGI and will not work without it. */ |
| 76 |
if( !location.origin || !location.origin.match || !location.origin.match(/http/) ){ |
| 77 |
document.getElementById("search_menubutton").style.display = "none"; |
| 78 |
} |
| 79 |
/* Used by the Hide/Show button beside syntax diagrams, to toggle the */ |
| 80 |
function hideorshow(btn,obj){ |
| 81 |
var x = document.getElementById(obj); |
| 82 |
var b = document.getElementById(btn); |
| 83 |
if( x.style.display!='none' ){ |
| 84 |
x.style.display = 'none'; |
| 85 |
b.innerHTML='show'; |
| 86 |
}else{ |
| 87 |
x.style.display = ''; |
| 88 |
b.innerHTML='hide'; |
| 89 |
} |
| 90 |
return false; |
| 91 |
} |
| 92 |
var antiRobot = 0; |
| 93 |
function antiRobotGo(){ |
| 94 |
if( antiRobot!=3 ) return; |
| 95 |
antiRobot = 7; |
| 96 |
var j = document.getElementById("mtimelink"); |
| 97 |
if(j && j.hasAttribute("data-href")) j.href=j.getAttribute("data-href"); |
| 98 |
} |
| 99 |
function antiRobotDefense(){ |
| 100 |
document.body.onmousedown=function(){ |
| 101 |
antiRobot |= 2; |
| 102 |
antiRobotGo(); |
| 103 |
document.body.onmousedown=null; |
| 104 |
} |
| 105 |
document.body.onmousemove=function(){ |
| 106 |
antiRobot |= 2; |
| 107 |
antiRobotGo(); |
| 108 |
document.body.onmousemove=null; |
| 109 |
} |
| 110 |
setTimeout(function(){ |
| 111 |
antiRobot |= 1; |
| 112 |
antiRobotGo(); |
| 113 |
}, 100) |
| 114 |
antiRobotGo(); |
| 115 |
} |
| 116 |
antiRobotDefense(); |
| 117 |
</script> |
| 118 |
<?xml version="1.0" encoding="Windows-1252"?> |
| 119 |
|
| 120 |
|
| 121 |
<a name="2015_11_02"></a><h3>2015-11-02 - Release 3.9.2</h3><blockquote> |
| 122 |
<p>SQLite <a href="releaselog/3_9_2.html">version 3.9.2</a> is a patch release fixing two obscure bugs. |
| 123 |
(Details: <a href="https://sqlite.org/src/tktview?name=8a2adec166">(1)</a>, |
| 124 |
<a href="https://sqlite.org/src/tktview?name=ac661962a2">(2)</a>). |
| 125 |
Upgrade only if you are having problems. |
| 126 |
</blockquote><hr width="50%"><a name="2015_10_16"></a><h3>2015-10-16 - Release 3.9.1</h3><blockquote> |
| 127 |
<p>SQLite <a href="releaselog/3_9_1.html">version 3.9.1</a> is a |
| 128 |
<a href="https://sqlite.org/src/vpatch?from=version-3.9.0&to=version-3.9.1">small patch</a> |
| 129 |
to <a href="releaselog/3_9_0.html">version 3.9.0</a> that includes |
| 130 |
a few simple build script and #ifdef tweaks to make the code easier to |
| 131 |
compile on a wider variety of platform. There are no functional changes, |
| 132 |
except for a single |
| 133 |
<a href="https://sqlite.org/src/info/57eec374ae1d0a1d4a">minor bug-fix</a> in |
| 134 |
<a href="json1.html">the json1 extension</a> to stop it from recognizing form-feed |
| 135 |
(ASCII 0x0c) as a whitespace character, in conformance with |
| 136 |
<a href="http://www.rfc-editor.org/rfc/rfc7159.txt">RFC7159</a>. |
| 137 |
</blockquote><hr width="50%"><a name="2015_10_14"></a><h3>2015-10-14 - Release 3.9.0</h3><blockquote> |
| 138 |
<p>SQLite version 3.9.0 is a regularly schedule maintenance release. |
| 139 |
Key changes include: |
| 140 |
<ul> |
| 141 |
<li>Begin using <a href="http://semver.org/">semantic versioning</a>. |
| 142 |
<li><a href="json1.html">JSON SQL functions</a> |
| 143 |
<li>The <a href="fts5.html">FTS5</a> full-text search engine |
| 144 |
<li>Support for <a href="expridx.html">indexes on expressions</a> |
| 145 |
<li>Support for <a href="vtab.html#tabfunc2">table-valued functions</a> |
| 146 |
</ul> |
| 147 |
See the <a href="releaselog/3_9_0.html">change log</a> for a long and more complete list |
| 148 |
of changes. |
| 149 |
</blockquote><hr width="50%"><a name="2015_07_29"></a><h3>2015-07-29 - Release 3.8.11.1</h3><blockquote> |
| 150 |
<p>SQLite version 3.8.11.1 is a patch release that fixes two arcane |
| 151 |
issues that were reported shortly after 3.8.11 was released. Upgrade |
| 152 |
from 3.8.11 only in the unlikely event that one of these obscure |
| 153 |
issues affect your code. |
| 154 |
</blockquote><hr width="50%"><a name="2015_07_27"></a><h3>2015-07-27 - Release 3.8.11</h3><blockquote> |
| 155 |
<p>SQLite version 3.8.11 is a regularly scheduled maintenance release. |
| 156 |
See the <a href="releaselog/3_8_11.html">change log</a> for details. |
| 157 |
</blockquote><hr width="50%"><a name="2015_05_20"></a><h3>2015-05-20 - Release 3.8.10.2</h3><blockquote> |
| 158 |
<p>Yikes! Index corruption after a sequence of valid SQL statements! |
| 159 |
<p>It has been many years since anything like |
| 160 |
<a href="https://sqlite.org/src/info/34cd55d6">this bug</a> has snuck into |
| 161 |
an official SQLite release. But for the pasts seven months |
| 162 |
(<a href="releaselog/3_8_7.html">version 3.8.7</a> through <a href="releaselog/3_8_10_1.html">version 3.8.10.1</a>) |
| 163 |
if you do an INSERT into a carefully |
| 164 |
crafted schema in which there are two nested triggers that convert |
| 165 |
an index key value from TEXT to INTEGER and then back |
| 166 |
to TEXT again, the INTEGER value might get inserted as the index |
| 167 |
key instead of the correct TEXT, resulting in index corruption. |
| 168 |
This patch release adds a single line of code to fix the problem. |
| 169 |
<p>If you do actually encounter this problem, running <a href="lang_reindex.html">REINDEX</a> on the |
| 170 |
damaged indexes will clear it. |
| 171 |
</blockquote><hr width="50%"><a name="2015_05_09"></a><h3>2015-05-09 - Release 3.8.10.1</h3><blockquote> |
| 172 |
<p>The 3.8.10 release did not add the new <a href="compile.html#enable_dbstat_vtab">SQLITE_ENABLE_DBSTAT_VTAB</a> |
| 173 |
compile-time option to the <a href="c3ref/compileoption_get.html">sqlite3_compileoption_used()</a> interface. |
| 174 |
This patch release fixes that omission. And while we are at it, |
| 175 |
the associated <a href="dbstat.html">dbstat virtual table</a> was enhanced slightly and a |
| 176 |
harmless compiler warning was fixed.</p> |
| 177 |
|
| 178 |
<p> <p>There is no reason to upgrade from version 3.8.10 unless you are |
| 179 |
using the new <a href="compile.html#enable_dbstat_vtab">SQLITE_ENABLE_DBSTAT_VTAB</a> compile-time option. |
| 180 |
</blockquote><hr width="50%"><a name="2015_05_07"></a><h3>2015-05-07 - Release 3.8.10</h3><blockquote> |
| 181 |
<p>SQLite version 3.8.10 is a regularly scheduled maintenance release. |
| 182 |
This release features performance improvements, fixes to several |
| 183 |
arcane bugs found by the AFL fuzzer, the new "sqldiff.exe" command-line |
| 184 |
utility, improvements to the documentation, and other enhancements. |
| 185 |
See the <a href='releaselog/3_8_10.html'>release notes</a> for |
| 186 |
additional information. |
| 187 |
</blockquote><hr width="50%"><a name="2015_04_08"></a><h3>2015-04-08 - Release 3.8.9</h3><blockquote> |
| 188 |
<p>SQLite version 3.8.9 is a regularly scheduled maintenance release. |
| 189 |
New features in this release include the |
| 190 |
<a href="pragma.html#pragma_index_xinfo">PRAGMA index_xinfo</a> command, the <a href="c3ref/status.html">sqlite3_status64()</a> interface, |
| 191 |
and the ".dbinfo" command of the <a href="cli.html">command-line shell</a>. |
| 192 |
See the <a href='releaselog/3_8_9.html'>release notes</a> for |
| 193 |
additional information. |
| 194 |
</blockquote><hr width="50%"><a name="2015_02_25"></a><h3>2015-02-25 - Release 3.8.8.3</h3><blockquote> |
| 195 |
<p>The 3.8.8.3 patch release fixes an obscure problem in the SQLite code |
| 196 |
generator that can cause incorrect results when the qualifying expression |
| 197 |
of a <a href="partialindex.html">partial index</a> is used inside the ON clause of a LEFT JOIN. |
| 198 |
This problem has been in the code since support for partial indexes |
| 199 |
was first added in version 3.8.0. However, it is difficult to imagine |
| 200 |
a valid reason to every put the qualifying constraint inside the ON |
| 201 |
clause of a LEFT JOIN, and so this issue has never come up before.</p> |
| 202 |
|
| 203 |
<p><p>Any applications that is vulnerable to this bug would have encountered |
| 204 |
problems already. Hence, upgrading from the previous release is optional. |
| 205 |
</blockquote><hr width="50%"><a name="2015_01_30"></a><h3>2015-01-30 - Release 3.8.8.2</h3><blockquote> |
| 206 |
<p>The 3.8.8.2 patch release fixes a single minor problem: It ensures |
| 207 |
that the <a href="c3ref/wal_checkpoint.html">sqlite3_wal_checkpoint(TRUNCATE)</a> operation will always truncate |
| 208 |
the <a href="wal.html">write-ahead log</a> even if log had already been reset and contained |
| 209 |
no new content. It is unclear if this is a bug fix or a new feature.</p> |
| 210 |
|
| 211 |
<p><p>Something like this would normally go into the next regularly scheduled |
| 212 |
release, but a prominent SQLite user needed the change in a hurry so |
| 213 |
we were happy to rush it out via this patch.</p> |
| 214 |
|
| 215 |
<p><p>There is no reason to upgrade unless you actually need the enhanced |
| 216 |
behavior of <a href="c3ref/wal_checkpoint.html">sqlite3_wal_checkpoint(TRUNCATE)</a>. |
| 217 |
</blockquote><hr width="50%"><a name="2015_01_20"></a><h3>2015-01-20 - Release 3.8.8.1</h3><blockquote> |
| 218 |
<p>Within hours of releasing version 3.8.8, a bug was reported against |
| 219 |
the 10-month-old 3.8.4 release. As that bug exists in all subsequent |
| 220 |
releases, the decision was made to issue a small patch to the |
| 221 |
3.8.8 before it came into widespread use.</p> |
| 222 |
|
| 223 |
<p><p>See ticket |
| 224 |
<a href="https://sqlite.org/src/info/f97c4637102a3ae72b7911">f97c4637102a3ae72b7911</a> |
| 225 |
for a description of the bug.</p> |
| 226 |
|
| 227 |
<p><p>The changes between versions 3.8.8 and 3.8.8.1 are minimal. |
| 228 |
</blockquote><hr width="50%"><a name="2015_01_16"></a><h3>2015-01-16 - Release 3.8.8</h3><blockquote> |
| 229 |
<p>SQLite <a href="releaselog/3_8_8.html">version 3.8.8</a> is a regularly schedule maintenance release of |
| 230 |
SQLite.</p> |
| 231 |
|
| 232 |
<p><p>There are no dramatic new features or performance enhancements in this |
| 233 |
release, merely incremental improvements. Most of the performance gain |
| 234 |
in this release comes from refactoring the B-Tree rebalancing logic to |
| 235 |
avoid unnecessary memcpy() operations. New features include the |
| 236 |
<a href="pragma.html#pragma_data_version">PRAGMA data_version</a> statement and the ability to accept a |
| 237 |
<a href="lang_select.html#values">VALUES clause</a> with no arbitrary limit on the number of rows. |
| 238 |
Several obscure bugs have been fixed, including some multithreading |
| 239 |
races and a work-around for a compiler bug on some Macs.</p> |
| 240 |
|
| 241 |
<p><p>See the <a href="releaselog/3_8_8.html">change log</a> for a longer list of |
| 242 |
enhancements and bug fixes. |
| 243 |
</blockquote><hr width="50%"><a name="2014_12_09"></a><h3>2014-12-09 - Release 3.8.7.4</h3><blockquote> |
| 244 |
<p>SQLite <a href="releaselog/3_8_7_4.html">version 3.8.7.4</a> an unscheduled bug-fix release. Changes from |
| 245 |
the previous release and from <a href="releaselog/3_8_7.html">version 3.8.7</a> are minimal.</p> |
| 246 |
|
| 247 |
<p><p>This release fixes adds in a mutex that is required by the changes of |
| 248 |
the 3.8.7.3 patch but was accidentally omitted. The mutex was not required |
| 249 |
by any of the internal SQLite tests, but Firefox crashes without it. |
| 250 |
Test cases have been added to ensure that mutex is never again missed. |
| 251 |
</blockquote><hr width="50%"><a name="2014_12_06"></a><h3>2014-12-06 - Release 3.8.7.3</h3><blockquote> |
| 252 |
<p>SQLite <a href="releaselog/3_8_7_3.html">version 3.8.7.3</a> an unscheduled bug-fix release. Changes from |
| 253 |
the previous release and from <a href="releaselog/3_8_7.html">version 3.8.7</a> are minimal.</p> |
| 254 |
|
| 255 |
<p><p>This release fixes two obscure bugs that can result in incorrect |
| 256 |
query results and/or application crashes, but not (as far as we can |
| 257 |
tell) security vulnerabilities. Both bugs have been latent in the |
| 258 |
code across multiple prior releases and have never before been encountered, |
| 259 |
so they are unlikely to cause problems. Nevertheless |
| 260 |
it seems prudent to publish fixes for them both. See the |
| 261 |
change log for details. |
| 262 |
</blockquote><hr width="50%"><a name="2014_11_19"></a><h3>2014-11-19 - Release 3.8.7.2</h3><blockquote> |
| 263 |
<p>SQLite <a href="releaselog/3_8_7_2.html">version 3.8.7.2</a> is a patch and bug-fix release. Changes from |
| 264 |
the previous release are minimal.</p> |
| 265 |
|
| 266 |
<p><p>The primary reason for this release is to enhance the <a href="lang_transaction.html">ROLLBACK</a> command |
| 267 |
so that it allows running queries on the same database connection to |
| 268 |
continue running as long as the ROLLBACK does not change the schema. |
| 269 |
In all previous versions of SQLite, a ROLLBACK would cause pending |
| 270 |
queries to stop immediately and return <a href="rescode.html#abort">SQLITE_ABORT</a> or |
| 271 |
<a href="rescode.html#abort_rollback">SQLITE_ABORT_ROLLBACK</a>. Pending queries still abort if the ROLLBACK |
| 272 |
changes the database schema, but as of this patch release, the queries |
| 273 |
are allowed to continue running if the schema is unmodified.</p> |
| 274 |
|
| 275 |
<p><p>In addition to the ROLLBACK enhancement, this patch release also |
| 276 |
includes fixes for three obscure bugs. See the |
| 277 |
<a href="releaselog/3_8_7_2.html">change log</a> for details. |
| 278 |
</blockquote><hr width="50%"><a name="2014_10_30"></a><h3>2014-10-30 - Release 3.8.7.1</h3><blockquote> |
| 279 |
<p>SQLite <a href="releaselog/3_8_7_1.html">version 3.8.7.1</a> is a bug-fix release.</p> |
| 280 |
|
| 281 |
<p><p>The primary reason for this bug-fix release is to address a problem with |
| 282 |
updating the value of fields at the end of a table that were added |
| 283 |
using <a href="lang_altertable.html">ALTER TABLE ADD COLUMN</a>. This problem |
| 284 |
<a href="https://sqlite.org/src/info/43107840f1c02">1</a> first appeared in the |
| 285 |
3.8.7 release.</p> |
| 286 |
|
| 287 |
<p><p>Another minor annoyance in the 3.8.7 release was the fact that the |
| 288 |
Android build tried to use the strchrnul() function from the standard |
| 289 |
C library but that function is not available on Android. Android builds |
| 290 |
had to add -DHAVE_STRCHRNUL=0 to work around the problem. This patch |
| 291 |
fixes that so that Android builds should now work without any changes.</p> |
| 292 |
|
| 293 |
<p><p>The operation of <a href="pragma.html#pragma_journal_mode">PRAGMA journal_mode=TRUNCATE</a> has been enhanced so that |
| 294 |
it invokes fsync() after truncating the journal file when |
| 295 |
<a href="pragma.html#pragma_synchronous">PRAGMA synchronous=FULL</a>. This helps to preserve transaction durability |
| 296 |
in the case of a power loss occurring shortly after commit.</p> |
| 297 |
|
| 298 |
<p><p>Finally, a couple of long-standing and obscure problems associated with run |
| 299 |
UPDATE and DELETE on VIEWs were fixed.</p> |
| 300 |
|
| 301 |
<p><p>The <a href="https://sqlite.org/src/vdiff?from=e4ab094f8afce0817f4074e823fabe59fc29ebb4&to=83afe23e553e802c0947c80d0ffdd120423e7c52&sbs=1">changes from 3.8.7</a> are minimal. |
| 302 |
</blockquote><hr width="50%"><a name="2014_10_17"></a><h3>2014-10-17 - Release 3.8.7</h3><blockquote> |
| 303 |
<p>SQLite <a href="releaselog/3_8_7.html">version 3.8.7</a> is a regularly scheduled maintenance release. |
| 304 |
Upgrading from all prior versions is recommended.</p> |
| 305 |
|
| 306 |
<p><p>Most of the changes from the previous release have been micro-optimizations |
| 307 |
designed to help SQLite run a little faster. Each individual optimization |
| 308 |
has an unmeasurably small performance impact. But the improvements add up. |
| 309 |
Measured on a well-defined workload (which the SQLite developers use |
| 310 |
as a proxy for a typical application workload) using cachegrind on Linux |
| 311 |
and compiled with gcc 4.8.1 and -Os on x64 linux, the current release |
| 312 |
does over 20% more work for the same number of CPU cycles compared to the |
| 313 |
previous release. Cachegrind is not a real CPU, and the workload |
| 314 |
used for measurement is only a proxy. So your performance may vary. |
| 315 |
We expect to see about half the measured and reported improvement in |
| 316 |
real-world applications. 10% is less than 20% but it is still pretty |
| 317 |
good, we think.</p> |
| 318 |
|
| 319 |
<p><p>This release includes a new set of C-language interfaces that have |
| 320 |
unsigned 64-bit instead of signed 32-bit length parameters. The new |
| 321 |
APIs do not provide any new capabilities. But they do make it easier |
| 322 |
to write applications that are more resistant to integer overflow |
| 323 |
vulnerabilities.</p> |
| 324 |
|
| 325 |
<p><p>This release also includes a new sorter that is able to use multiple |
| 326 |
threads to help with large sort operations. (Sort operations are |
| 327 |
sometimes required to implement ORDER BY and/or GROUP BY clauses and |
| 328 |
are almost always required for CREATE INDEX.) The multi-threads sorter |
| 329 |
is turned off by default and must be enabled using the |
| 330 |
<a href="pragma.html#pragma_threads">PRAGMA threads</a> SQL command. Note that the multi-threaded sorter |
| 331 |
provides faster real-time performance for large sorts, but it also |
| 332 |
uses more CPU cycles and more energy. |
| 333 |
</blockquote><hr width="50%"><a name="2014_08_15"></a><h3>2014-08-15 - Release 3.8.6</h3><blockquote> |
| 334 |
<p>SQLite <a href="releaselog/3_8_6.html">version 3.8.6</a> is a regularly scheduled maintenance release. |
| 335 |
Upgrading from all previous versions is recommended.</p> |
| 336 |
|
| 337 |
<p><p>This release contains the usual assortment of obscure bug fixes. |
| 338 |
One bug, however, deserves special attention. |
| 339 |
A problem appeared in the <a href="lang_createindex.html">CREATE INDEX</a> command beginning with |
| 340 |
<a href="releaselog/3_8_2.html">version 3.8.2</a> (2013-12-06) that allowed, under some circumstances, |
| 341 |
a UNIQUE index to be created on a column that was not unique. Once |
| 342 |
the index was created, no new non-unique entries could be inserted, but |
| 343 |
preexisting non-unique entries would remain. See ticket |
| 344 |
<a href="https://sqlite.org/src/info/9a6daf340df99ba93c">9a6daf340df99ba93c</a> |
| 345 |
for further information. In addition to fixing this bug, the |
| 346 |
<a href="pragma.html#pragma_integrity_check">PRAGMA integrity_check</a> command has been enhanced to detect |
| 347 |
non-uniqueness in UNIQUE indices, so that if this bug did introduce |
| 348 |
any problems in databases, those problems can be easily detected.</p> |
| 349 |
|
| 350 |
<p><p>Other noteworthy changes include the addition of support for |
| 351 |
<a href="lang_expr.html#hexint">hexadecimal integers</a> (ex: 0x1234), and performance enhancements |
| 352 |
to the <a href="lang_expr.html#in_op">IN operator</a> which, according to |
| 353 |
<a href="http://www.mail-archive.com/sqlite-users%40sqlite.org/msg85350.html">mailing list reports</a>, |
| 354 |
help some queries run up to five times faster.</p> |
| 355 |
|
| 356 |
<p><p>Version 3.8.6 uses 25% fewer CPU cycles than version 3.8.0 from |
| 357 |
approximately one year ago, according to <a href="http://valgrind.org/">valgrind</a> |
| 358 |
and the |
| 359 |
<a href="https://sqlite.org/src/artifact/d29c8048beb7e">test/speedtest1.c</a> |
| 360 |
test program. |
| 361 |
On the other hand, |
| 362 |
the compiled binary for version 3.8.6 is about 5% larger than 3.8.0. |
| 363 |
The size increase is |
| 364 |
due in part to the addition of new features such as <a href="withoutrowid.html">WITHOUT ROWID</a> |
| 365 |
tables and <a href="lang_with.html">common table expressions</a>. |
| 366 |
</blockquote><hr width="50%"><a name="2014_06_04"></a><h3>2014-06-04 - Release 3.8.5</h3><blockquote> |
| 367 |
<p>SQLite <a href="releaselog/3_8_5.html">version 3.8.5</a> is a regularly scheduled maintenance release. |
| 368 |
Upgrading from the previous version is recommended.</p> |
| 369 |
|
| 370 |
<p><p>Version 3.8.5 fixes more than a dozen obscure bugs. None of these |
| 371 |
bugs should be a problem for existing applications. Nor do any of |
| 372 |
the bugs represent a security vulnerability. Nevertheless, upgrading |
| 373 |
is recommended to prevent future problems.</p> |
| 374 |
|
| 375 |
<p><p>In addition to bug fixes, the 3.8.5 release adds improvements to the |
| 376 |
query planner, especially regarding sorting using indices and handling |
| 377 |
OR terms |
| 378 |
in the WHERE clause for WITHOUT ROWID tables. The ".system" and |
| 379 |
".once" dot-commands were added to the command-line interface. And |
| 380 |
there were enhancements to the FTS4 and RTREE virtual tables. See |
| 381 |
the change log for details. |
| 382 |
</blockquote><hr width="50%"><a name="2014_04_03"></a><h3>2014-04-03 - Release 3.8.4.3</h3><blockquote> |
| 383 |
<p>The optimizations added in <a href="releaselog/3_8_4.html">version 3.8.4</a> caused some queries that involve |
| 384 |
subqueries in the FROM clause, DISTINCT, and ORDER BY clauses, to give an incorrect |
| 385 |
result. See |
| 386 |
<a href="https://sqlite.org/src/info/98825a79ce145686392d8074032ae54863aa21a3">ticket 98825a79ce145</a> |
| 387 |
for details. |
| 388 |
This release adds a |
| 389 |
<a href="https://sqlite.org/src/fdiff?sbs=1&v1=7d539cedb1c&v2=ebad891b7494d&smhdr">one-character change</a> |
| 390 |
to a single line of code to fix the problem. |
| 391 |
</blockquote><hr width="50%"><a name="2014_03_26"></a><h3>2014-03-26 - Release 3.8.4.2</h3><blockquote> |
| 392 |
<p>The code changes that resulted in the performance improvements |
| 393 |
in <a href="releaselog/3_8_4.html">version 3.8.4</a> missed a single buffer overflow test, which could |
| 394 |
result in a read past the end of a buffer while searching a database |
| 395 |
that is corrupted in a particular way. <a href="releaselog/3_8_4_2.html">Version 3.8.4.2</a> fixes that |
| 396 |
problem using a |
| 397 |
<a href="https://sqlite.org/src/fdiff?v1=e45e3f9daf38c5be&v2=714df4e1c82f629d&sbs=1">one-line patch</a>.</p> |
| 398 |
|
| 399 |
<p><p>We are not aware of any problems in <a href="releaselog/3_8_4.html">version 3.8.4</a> |
| 400 |
when working with well-formed database files. The problem fixed by this |
| 401 |
release only comes up when reading corrupt database files. |
| 402 |
</blockquote><hr width="50%"><a name="2014_03_11"></a><h3>2014-03-11 - Release 3.8.4.1</h3><blockquote> |
| 403 |
<p>SQLite <a href="releaselog/3_8_4_1.html">version 3.8.4.1</a> is a patch against <a href="releaselog/3_8_4.html">version 3.8.4</a> that fixes |
| 404 |
two minor issues: |
| 405 |
<ol> |
| 406 |
<li> Work around a C-preprocessor macro conflict that causes compilation |
| 407 |
problems for some configurations of Visual Studio. |
| 408 |
<li> Adjust the cost computation for the <a href="optoverview.html#skipscan">skip-scan optimization</a> for |
| 409 |
improved performance. |
| 410 |
</ol> |
| 411 |
Both of these issues came to light within minutes of tagging the previous |
| 412 |
release. Neither issue is serious but they can be annoying. Hence, the |
| 413 |
decision was made to do a quick patch release to address both issues. |
| 414 |
</blockquote><hr width="50%"><a name="2014_03_10"></a><h3>2014-03-10 - Release 3.8.4</h3><blockquote> |
| 415 |
<p>SQLite <a href="releaselog/3_8_4.html">version 3.8.4</a> is a maintenance release featuring performance |
| 416 |
enhancements and fixes for a number of obscure bugs. |
| 417 |
There are no significant new features in SQLite version 3.8.4. |
| 418 |
However, the number of CPU cycles (measured by valgrind) needed to |
| 419 |
do many common operations has be reduced by about 12% relative to the |
| 420 |
previous release, and by about 25% relative to <a href="releaselog/3_7_16.html">version 3.7.16</a> |
| 421 |
from approximately one year ago.</p> |
| 422 |
|
| 423 |
<p><p>Version 3.8.4 of SQLite fixes several corner-case bugs that were |
| 424 |
found since the previous release. These bugs were unlikely to appear |
| 425 |
in practice, and none represent a security vulnerability. |
| 426 |
Nevertheless, developers are encouraged to upgrade from all prior releases. |
| 427 |
</blockquote><hr width="50%"><a name="2014_02_11"></a><h3>2014-02-11 - Release 3.8.3.1</h3><blockquote> |
| 428 |
<p>SQLite <a href="releaselog/3_8_3_1.html">version 3.8.3.1</a> fixes a bug present in versions 3.8.1, |
| 429 |
3.8.2 and 3.8.3 that can cause queries to omit valid output rows. |
| 430 |
Upgrading from those versions is recommended.</p> |
| 431 |
|
| 432 |
<p><p>The problem only comes up if SQLite is compiled with either the |
| 433 |
<a href="compile.html#enable_stat3">SQLITE_ENABLE_STAT3</a> or <a href="compile.html#enable_stat4">SQLITE_ENABLE_STAT4</a> compile-time options. |
| 434 |
In that case, if a query has a WHERE clause that contains expressions |
| 435 |
like this: |
| 436 |
<blockquote> |
| 437 |
WHERE (expr1 OR expr2 OR ... OR exprN) AND column IS NOT NULL |
| 438 |
</blockquote> |
| 439 |
Where all of expr1 through exprN are suitable for use by indexes, |
| 440 |
then during query planning SQLite might mistakenly converted |
| 441 |
the "column IS NOT NULL" term into "column>NULL". But the latter |
| 442 |
term is never true, and so the query would return no rows.</p> |
| 443 |
|
| 444 |
<p><p>The trouble ticket for this bug is |
| 445 |
[<a href="https://sqlite.org/src/info/4c86b126f2">4c86b126f2</a>]. |
| 446 |
It is recommended that all users upgrade to avoid this problem. |
| 447 |
</blockquote><hr width="50%"><a name="2014_02_03"></a><h3>2014-02-03 - Release 3.8.3</h3><blockquote> |
| 448 |
<p>SQLite <a href="releaselog/3_8_3.html">version 3.8.3</a> is a regularly scheduled maintenance release. |
| 449 |
Upgrading from the previous release is optional.</p> |
| 450 |
|
| 451 |
<p> <p>The most visible change in version 3.8.3 is the addition of |
| 452 |
support for <a href="lang_with.html">common table expressions</a>. It is now possible to write a |
| 453 |
single <a href="lang_select.html">SELECT</a> statement that will query a tree or graph, using either |
| 454 |
a depth-first or a breadth-first search. A single SQLite query will |
| 455 |
even <a href="lang_with.html#sudoku">solve Sudoku puzzles</a> or <a href="lang_with.html#mandelbrot">compute the Mandelbrot set</a>. As part |
| 456 |
of this change, SQLite now accepts a <a href="lang_select.html#values">VALUES clause</a> anyplace that |
| 457 |
a <a href="lang_select.html">SELECT</a> statement is valid.</p> |
| 458 |
|
| 459 |
<p> <p>This release also includes many small performance enhancements which |
| 460 |
should give a small speed boost to legacy applications. And there are |
| 461 |
other minor enhancements such as the addition of the <a href="lang_corefunc.html#printf">printf()</a> SQL |
| 462 |
function. See the <a href="releaselog/3_8_3.html">change log</a> for details. |
| 463 |
</blockquote><hr width="50%"><a name="2013_12_06"></a><h3>2013-12-06 - Release 3.8.2</h3><blockquote> |
| 464 |
<p>SQLite <a href="releaselog/3_8_2.html">version 3.8.2</a> is a regularly scheduled maintenance release. |
| 465 |
Upgrading from the previous release is optional.</p> |
| 466 |
|
| 467 |
<p> <p>Version 3.8.2 adds support for <a href="withoutrowid.html">WITHOUT ROWID</a> tables. This is a |
| 468 |
significant extension to SQLite. Database files that contain WITHOUT ROWID |
| 469 |
tables are not readable or writable by prior versions of SQLite, however |
| 470 |
databases that do not use WITHOUT ROWID tables are fully backwards |
| 471 |
and forwards compatible.</p> |
| 472 |
|
| 473 |
<p> <p>The 3.8.2 release contains a potentially incompatible change. In |
| 474 |
all prior versions of SQLite, a <a href="lang_expr.html#castexpr">cast</a> from a very large positive |
| 475 |
floating point number into an integer resulted in the most negative integer. |
| 476 |
In other words, CAST(+99.9e99 to INT) would yield -9223372036854775808. |
| 477 |
This behavior came about because it is what x86/x64 hardware does |
| 478 |
for the equivalent cast in the C language. But the behavior is |
| 479 |
bizarre. And so it has been changed effective with this release so that |
| 480 |
a cast from a floating point number into an integer returns the integer |
| 481 |
between the floating point value and zero that is closest to the floating |
| 482 |
point value. Hence, CAST(+99.9e99 to INT) now returns +9223372036854775807. |
| 483 |
Since routines like <a href="c3ref/column_blob.html">sqlite3_column_int64()</a> do an implicit cast if the |
| 484 |
value being accessed is really a floating point number, they are also |
| 485 |
affected by this change.</p> |
| 486 |
|
| 487 |
<p> <p>Besides the two changes mentioned above, the 3.8.2 release also |
| 488 |
includes a number of performance enhancements. The |
| 489 |
<a href="optoverview.html#skipscan">skip-scan optimization</a> is now available for databases that have been |
| 490 |
processed by <a href="lang_analyze.html">ANALYZE</a>. Constant SQL functions are now factored out of |
| 491 |
inner loops, which can result in a significant speedup for queries that |
| 492 |
contain WHERE clause terms like "date>datetime('now','-2 days')". And |
| 493 |
various high-runner internal routines have been refactored for reduced |
| 494 |
CPU load. |
| 495 |
</blockquote><hr width="50%"><a name="2013_10_17"></a><h3>2013-10-17 - Release 3.8.1</h3><blockquote> |
| 496 |
<p>SQLite <a href="releaselog/3_8_1.html">version 3.8.1</a> is a regularly scheduled maintenance release. |
| 497 |
Upgrading from the previous release is optional, though you should upgrade |
| 498 |
if you are using <a href="partialindex.html">partial indices</a> as there was a |
| 499 |
<a href="https://sqlite.org/src/info/a5c8ed66ca">bug</a> related to partial |
| 500 |
indices in the previous release that could result in an incorrect answer |
| 501 |
for count(*) queries.</p> |
| 502 |
|
| 503 |
<p> <p>The <a href="queryplanner-ng.html">next generation query planner</a> that was premiered in the previous |
| 504 |
release continues to work well. |
| 505 |
The new query planner has been tweaked slightly |
| 506 |
in the current release to help it make better decisions in some |
| 507 |
cases, but is largely unchanged. Two new SQL functions, <a href="lang_corefunc.html#likelihood">likelihood()</a> and |
| 508 |
<a href="lang_corefunc.html#unlikely">unlikely()</a>, have been added to allow developers to give hints to the |
| 509 |
query planner without forcing the query planner into a particular decision.</p> |
| 510 |
|
| 511 |
<p> <p>Version 3.8.1 is the first SQLite release to take into account the |
| 512 |
estimated size of table and index rows when choosing a query plan. |
| 513 |
Row size estimates are based on the declared datatypes of columns. |
| 514 |
For example, a column of type VARCHAR(1000) is assumed |
| 515 |
to use much more space than a column of type INT. The datatype-based |
| 516 |
row size estimate can be |
| 517 |
overridden by appending a term of the form "sz=NNN" (where NNN is the |
| 518 |
average row size in bytes) to the end of the <a href="fileformat2.html#stat1tab">sqlite_stat1.stat</a> |
| 519 |
record for a table or index. Currently, row sizes are only used to help the |
| 520 |
query planner choose between a table or one of its indices when doing a |
| 521 |
table scan or a count(*) operation, though future releases are likely |
| 522 |
to use the estimated row size in other contexts as well. The new |
| 523 |
<a href="pragma.html#pragma_stats">PRAGMA stats</a> statement can be used to view row size estimates.</p> |
| 524 |
|
| 525 |
<p> <p>Version 3.8.1 adds the <a href="compile.html#enable_stat4">SQLITE_ENABLE_STAT4</a> compile-time option. |
| 526 |
STAT4 is very similar to STAT3 in that it uses samples from indices to |
| 527 |
try to guess how many rows of the index will be satisfy by WHERE clause |
| 528 |
constraints. The difference is that STAT4 samples all columns of the |
| 529 |
index whereas the older STAT3 only sampled the left-most column. Users |
| 530 |
of STAT3 are encouraged to upgrade to STAT4. Application developers should |
| 531 |
use STAT3 and STAT4 with caution since both options, by design, violate |
| 532 |
the <a href="queryplanner-ng.html#qpstab">query planner stability guarantee</a>, making it more difficult to ensure |
| 533 |
uniform performance is widely-deployed and mass-produced embedded |
| 534 |
applications. |
| 535 |
</blockquote><hr width="50%"><a name="2013_09_03"></a><h3>2013-09-03 - Release 3.8.0.2</h3><blockquote> |
| 536 |
<p>SQLite <a href="releaselog/3_8_0_2.html">version 3.8.0.2</a> contains a one-line fix to a bug in the |
| 537 |
new optimization that tries to omit unused LEFT JOINs from a query. |
| 538 |
</blockquote><hr width="50%"><a name="2013_08_29"></a><h3>2013-08-29 - Release 3.8.0.1</h3><blockquote> |
| 539 |
<p>SQLite <a href="releaselog/3_8_0_1.html">version 3.8.0.1</a> fixes some obscure bugs that were uncovered by |
| 540 |
users in the 3.8.0 release. Changes from 3.8.0 are minimal. |
| 541 |
</blockquote><hr width="50%"><a name="2013_08_26"></a><h3>2013-08-26 - Release 3.8.0</h3><blockquote> |
| 542 |
<b>Do not fear the zero!</b></p> |
| 543 |
|
| 544 |
<p> <p>SQLite <a href="releaselog/3_8_0.html">version 3.8.0</a> might easily have been called "3.7.18" instead. |
| 545 |
However, this release features the cutover of the |
| 546 |
<a href="queryplanner-ng.html">next generation query planner</a> or <a href="queryplanner-ng.html">NGQP</a>, and there is a small chance of |
| 547 |
<a href="queryplanner-ng.html#hazards">breaking legacy programs</a> that |
| 548 |
rely on undefined behavior in previous SQLite releases, and so the |
| 549 |
minor version number was incremented for that reason. |
| 550 |
But the risks are low and there is a <a href="queryplanner-ng.html#howtofix">query planner checklist</a> is |
| 551 |
available to application developers to aid in avoiding problems.</p> |
| 552 |
|
| 553 |
<p> <p>SQLite <a href="releaselog/3_8_0.html">version 3.8.0</a> is actually one of the most heavily tested |
| 554 |
SQLite releases ever. Thousands and thousands of beta copies have |
| 555 |
be downloaded, and presumably tested, and there have been no problem |
| 556 |
reports.</p> |
| 557 |
|
| 558 |
<p> <p>In addition to the <a href="queryplanner-ng.html">next generation query planner</a>, the 3.8.0 release |
| 559 |
adds support for <a href="partialindex.html">partial indices</a>, as well as several other new features. |
| 560 |
See the <a href="releaselog/3_8_0.html">change log</a> for further detail. |
| 561 |
</blockquote><hr width="50%"><a name="2013_05_20"></a><h3>2013-05-20 - Release 3.7.17</h3><blockquote> |
| 562 |
SQLite <a href="releaselog/3_7_17.html">version 3.7.17</a> is a regularly schedule maintenance release. |
| 563 |
Visit the <a href="releaselog/3_7_17.html">change log</a> for a full explanation of the |
| 564 |
changes in this release.</p> |
| 565 |
|
| 566 |
<p> There are many bug fixes in version 3.7.17. But this does not indicate |
| 567 |
that 3.7.16 was a problematic release. All of the bugs in 3.7.17 are |
| 568 |
obscure and are unlikely to impact any particular application. And most |
| 569 |
of the bugs that are fixed in 3.7.17 predate 3.7.16 and have been in |
| 570 |
the code for years without ever before being noticed. |
| 571 |
Nevertheless, due to the large number of fixes, |
| 572 |
all users are encouraged to upgrade when possible. |
| 573 |
</blockquote><hr width="50%"><a name="2013_04_12"></a><h3>2013-04-12 - Release 3.7.16.2</h3><blockquote> |
| 574 |
SQLite <a href="releaselog/3_7_16_2.html">version 3.7.16.2</a> fixes a long-standing flaw in the Windows |
| 575 |
OS interface that |
| 576 |
can result in database corruption under a rare race condition. |
| 577 |
See <a href="https://sqlite.org/src/info/7ff3120e4f">https://sqlite.org/src/info/7ff3120e4f</a> for a full description |
| 578 |
of the problem.</p> |
| 579 |
|
| 580 |
<p> As far as we know, this bug has never been seen in the wild. The |
| 581 |
problem was discovered by the SQLite developers while writing stress tests |
| 582 |
for a separate component of SQLite. Those stress tests have not yet |
| 583 |
found any problems with the component they were intended to verify, but |
| 584 |
they did find the bug which is the subject of this patch release.</p> |
| 585 |
|
| 586 |
<p> Other than updates to version numbers, the only difference between this |
| 587 |
release and 3.7.16.1 is a two-character change in a single identifier, |
| 588 |
which is contained in the windows-specific OS interface logic. There |
| 589 |
are no changes in this release (other than version numbers) for platforms |
| 590 |
other than Windows. |
| 591 |
</blockquote><hr width="50%"><a name="2013_03_29"></a><h3>2013-03-29 - Release 3.7.16.1</h3><blockquote> |
| 592 |
SQLite <a href="releaselog/3_7_16_1.html">version 3.7.16.1</a> is a bug fix release that fixes a few problems |
| 593 |
that were present in the previous releases.</p> |
| 594 |
|
| 595 |
<p> The primary motivation for version 3.7.16.1 is to fix a bug in the |
| 596 |
query optimizer that was introduced as part of <a href="releaselog/3_7_15.html">version 3.7.15</a>. The |
| 597 |
query optimizer was being a little overzealous in optimizing out some |
| 598 |
ORDER BY clauses, which resulted in sorting being omitted on occasions |
| 599 |
where sorting is required to get the correct answer. See |
| 600 |
ticket <a href="https://sqlite.org/src/info/a179fe7465">a179fe7465</a> for |
| 601 |
details.</p> |
| 602 |
|
| 603 |
<p> In addition to the ORDER BY fix, several other patches to fix obscure |
| 604 |
(and mostly harmless) bugs and to fix spelling errors in source code |
| 605 |
comments are also included in this release. |
| 606 |
</blockquote><hr width="50%"><a name="2013_03_18"></a><h3>2013-03-18 - Release 3.7.16</h3><blockquote> |
| 607 |
SQLite <a href="releaselog/3_7_16.html">version 3.7.16</a> is a regularly scheduled release of SQLite. |
| 608 |
This release contains several language enhancements and improvements |
| 609 |
to the query optimizer. A list of the major enhancements and optimizations |
| 610 |
can be see on the <a href="releaselog/3_7_16.html">change log</a>.</p> |
| 611 |
|
| 612 |
<p> There was one important bug fix |
| 613 |
(see <a href="https://sqlite.org/src/info/fc7bd6358f">Ticket fc7bd6358f</a>) |
| 614 |
that addresses an incorrect query result that could have occurred in |
| 615 |
a three-way join where the join constraints compared INTEGER columns |
| 616 |
to TEXT columns. This issue had been in the code for time out of mind |
| 617 |
and had never before been reported, so we surmise that it is very obscure. |
| 618 |
Nevertheless, all users are advised to upgrade to avoid any future problems |
| 619 |
associated with this issue. |
| 620 |
</blockquote><hr width="50%"><a name="2013_01_09"></a><h3>2013-01-09 - Release 3.7.15.2</h3><blockquote> |
| 621 |
SQLite <a href="releaselog/3_7_15_2.html">version 3.7.15.2</a> is a patch release that fixes a single bug |
| 622 |
that was introduced in version <a href="releaselog/3_7_15.html">version 3.7.15</a>. The fix is a 4-character |
| 623 |
edit to a single line of code. Other than this 4-character change and |
| 624 |
the update of the version number, nothing has changed from |
| 625 |
<a href="releaselog/3_7_15_1.html">version 3.7.15.1</a>. |
| 626 |
</blockquote><hr width="50%"><a name="2012_12_19"></a><h3>2012-12-19 - Release 3.7.15.1</h3><blockquote> |
| 627 |
SQLite <a href="releaselog/3_7_15_1.html">version 3.7.15.1</a> is a patch release that fixes a single bug |
| 628 |
that was introduced in version <a href="releaselog/3_7_15.html">version 3.7.15</a>. The fix involved changing |
| 629 |
two lines of code and adding a single assert(). This release also includes |
| 630 |
some new test cases to prevent a regression of the bug, and the version |
| 631 |
number is increased, of course. But otherwise, nothing has changed from |
| 632 |
<a href="releaselog/3_7_15.html">version 3.7.15</a>. |
| 633 |
</blockquote><hr width="50%"><a name="2012_12_12"></a><h3>2012-12-12 - Release 3.7.15</h3><blockquote> |
| 634 |
SQLite <a href="releaselog/3_7_15.html">version 3.7.15</a> is a regularly schedule release of SQLite. This |
| 635 |
release contains several improvements to the query planner and optimizer |
| 636 |
and one important bug fix. This is the first release to officially |
| 637 |
support Windows 8 Phone.</p> |
| 638 |
|
| 639 |
<p> The important bug fix is a problem that can lead to segfaults when using |
| 640 |
<a href="sharedcache.html">shared cache mode</a> on a schema that contains a <a href="lang_expr.html#collateop">COLLATE operator</a> within |
| 641 |
a <a href="lang_createtable.html#ckconst">CHECK constraint</a> or within a <a href="lang_createview.html">view</a>. Collating functions are associated |
| 642 |
with individual database connections. But a pointer to the collating function |
| 643 |
was also being cached within expressions. If an expression was part of the |
| 644 |
schema and contained a cached collating function, it would point to the |
| 645 |
collating function in the database connection that originally parsed the |
| 646 |
schema. If that database connection closed while other database |
| 647 |
connections using the same shared cache continued to operate, they other |
| 648 |
database connections would try to use the deallocated collating function |
| 649 |
in the database connection that closed. The fix in version 3.7.15 was to |
| 650 |
not cache collating function pointers in the expression structure but |
| 651 |
instead look them up each time a new statement is prepared.</p> |
| 652 |
|
| 653 |
<p> This release also contains some important enhancements to the query planner |
| 654 |
which should (we hope) make some queries run faster. The enhancements |
| 655 |
include:</p> |
| 656 |
|
| 657 |
<p> <ol><li><p>When doing a full-table scan, try to use an index instead of |
| 658 |
the original table, under the theory that indices contain less information |
| 659 |
and are thus smaller and hence require less disk I/O to scan.</p></p> |
| 660 |
|
| 661 |
<p> <li><p>Enhance the <a href="lang_expr.html#in_op">IN operator</a> to allow it to make use of |
| 662 |
indices that have <a href="datatype3.html#affinity">numeric affinity</a>.</p></p> |
| 663 |
|
| 664 |
<p> <li><p>Do a better job of recognizing when an ORDER BY clause can be |
| 665 |
implemented using indices - especially in cases where the ORDER BY clause |
| 666 |
contains terms from two or more tables in a join.</p> |
| 667 |
</ol> |
| 668 |
</blockquote><hr width="50%"><a name="2012_10_04"></a><h3>2012-10-04 - Release 3.7.14.1</h3><blockquote> |
| 669 |
SQLite <a href="releaselog/3_7_14_1.html">version 3.7.14.1</a> is a patch release. Changes from the baseline |
| 670 |
version 3.7.14 are minimal and are restricted to fixing three bugs.</p> |
| 671 |
|
| 672 |
<p> One of the fixed bugs is a long-standing issue with the TCL interface. |
| 673 |
Another is an external compiler bug that SQLite merely works around and |
| 674 |
that only comes up if you are using the VisualStudio-2012 compiler to |
| 675 |
generate WinRT applications on ARM with optimizations enabled. The |
| 676 |
third problem is an SQLite core bug, introduced in version 3.7.14, that |
| 677 |
can cause a segfault if a query contains a LEFT JOIN that contains an OR |
| 678 |
in the ON clause. |
| 679 |
</blockquote><hr width="50%"><a name="2012_09_03"></a><h3>2012-09-03 - Release 3.7.14</h3><blockquote> |
| 680 |
SQLite <a href="releaselog/3_7_14.html">version 3.7.14</a> is a regularly scheduled maintenance release |
| 681 |
of SQLite. The previous release continues to work well. Upgrading |
| 682 |
is optional.</p> |
| 683 |
|
| 684 |
<p> Version 3.7.14 drops native support for OS/2. We are not aware of any |
| 685 |
active projects that were using SQLite on OS/2 and since the SQLite |
| 686 |
developers had no way of testing on OS/2 it seemed like it was time |
| 687 |
to simply remove the OS/2 code from the SQLite tree. If there are |
| 688 |
OS/2 projects out there that still need SQLite support, they can |
| 689 |
continue to maintain their own private <a href="vfs.html">VFS</a> which can be linked to |
| 690 |
SQLite at start-time using the <a href="c3ref/vfs_find.html">sqlite3_vfs_register()</a> interface.</p> |
| 691 |
|
| 692 |
<p> The <a href="c3ref/close.html">sqlite3_close_v2()</a> interface has been added. The sqlite3_close_v2() |
| 693 |
interface differs from sqlite3_close() in that it is designed to work |
| 694 |
better for host language that use a garbage collector. With the older |
| 695 |
sqlite3_close() interface, the associated <a href="c3ref/stmt.html">prepared statements</a> and |
| 696 |
<a href="c3ref/backup.html">sqlite3_backup</a> objects must be destroyed before the database connection. |
| 697 |
With the newer sqlite3_close_v2() interface, the objects can be destroyed |
| 698 |
in any order.</p> |
| 699 |
|
| 700 |
<p> This release also includes performance improvements to the sort algorithm |
| 701 |
that is used to implement ORDER BY and CREATE INDEX. And the query planner |
| 702 |
has been enhanced to better use covering indices on queries that use OR |
| 703 |
terms in the WHERE clause. |
| 704 |
</blockquote><hr width="50%"><a name="2012_06_11"></a><h3>2012-06-11 - Release 3.7.13</h3><blockquote> |
| 705 |
SQLite <a href="releaselog/3_7_13.html">version 3.7.13</a> adds support for WinRT and metro style |
| 706 |
applications for Microsoft Windows 8. The 3.7.13 release is |
| 707 |
coming sooner than is usual after the previous release in order to get |
| 708 |
this new capability into the hands of developers. To use SQLite in |
| 709 |
a metro style application, compile with the -DSQLITE_OS_WINRT flag. |
| 710 |
Because of the increased application security and safety requirements |
| 711 |
of WinRT, all database |
| 712 |
filenames should be full pathnames. Note that SQLite is not capable |
| 713 |
of accessing databases outside the installation directory and application |
| 714 |
data directory. This restriction is another security and safety feature |
| 715 |
of WinRT. Apart from these restrictions, SQLite should work exactly |
| 716 |
the same on WinRT as it does on every other system.</p> |
| 717 |
|
| 718 |
<p> Also in this release: when a database is opened using <a href="uri.html">URI filenames</a> |
| 719 |
and the <a href="uri.html#coreqp">mode=memory</a> query parameter |
| 720 |
then the database is an in-memory database, just as if it had |
| 721 |
been named ":memory:". But, if shared cache mode is enabled, then |
| 722 |
all other database connections that specify the same URI filename |
| 723 |
will connect to the same in-memory database. This allows two or more |
| 724 |
database connections (in the same process) to share the same in-memory |
| 725 |
database.</p> |
| 726 |
|
| 727 |
<p> This release also includes some corner-case performance optimizations |
| 728 |
that are obscure yet significant to an important subset of SQLite users. |
| 729 |
Getting these performance optimizations into circulation quickly is |
| 730 |
yet another reason for making this release so soon following the previous.</p> |
| 731 |
|
| 732 |
<p> The next release of SQLite is scheduled to occur after the usual |
| 733 |
2 or 3 month interval. |
| 734 |
</blockquote><hr width="50%"><a name="2012_05_22"></a><h3>2012-05-22 - Patch Release 3.7.12.1</h3><blockquote> |
| 735 |
SQLite <a href="releaselog/3_7_12_1.html">version 3.7.12.1</a> is a patch release for <a href="releaselog/3_7_12.html">version 3.7.12</a> that |
| 736 |
fixes a <a href="https://sqlite.org/src/info/c2ad16f997ee9c">bug</a> that was |
| 737 |
introduced in version 3.7.12 and that can |
| 738 |
cause a segfault for certain obscure nested aggregate queries. |
| 739 |
There are very few changes in 3.7.12.1, and upgrading is only needed for |
| 740 |
applications that do nested aggregate queries. |
| 741 |
</blockquote><hr width="50%"><a name="2012_05_14"></a><h3>2012-05-14 - Version 3.7.12</h3><blockquote> |
| 742 |
SQLite <a href="releaselog/3_7_12.html">version 3.7.12</a> is a regularly scheduled maintenance release. |
| 743 |
This release contains several new optimizations and bug fixes and upgrading |
| 744 |
is recommended. See the <a href="releaselog/3_7_12.html">change summary</a> for details. |
| 745 |
</blockquote><hr width="50%"><a name="2012_03_20"></a><h3>2012-03-20 - Version 3.7.11</h3><blockquote> |
| 746 |
SQLite <a href="releaselog/3_7_11.html">version 3.7.11</a> is a regularly scheduled maintenance release |
| 747 |
which was rushed out early due to a |
| 748 |
<a href="https://sqlite.org/src/info/b7c8682cc1">bug in the query optimizer</a> |
| 749 |
introduced in the previous release. The bug is obscure - it changes |
| 750 |
a LEFT JOIN into an INNER JOIN in some cases when there is a 3-way join |
| 751 |
and OR terms in the WHERE clause. But it was considered serious enough to |
| 752 |
rush out a fix. Apart from this one problem, SQLite <a href="releaselog/3_7_10.html">version 3.7.10</a> has |
| 753 |
not given any trouble. Upgrading to <a href="releaselog/3_7_11.html">version 3.7.11</a> from versions |
| 754 |
3.7.6.3, 3.7.7, 3.7.7.1, 3.7.8, or 3.7.9 is |
| 755 |
optional. Upgrading from other releases, including the previous release |
| 756 |
3.7.10, is recommended.</p> |
| 757 |
|
| 758 |
<p> Other enhancements found in this release are enumerated in the |
| 759 |
<a href="releaselog/3_7_11.html">change log</a>. |
| 760 |
</blockquote><hr width="50%"><a name="2012_01_16"></a><h3>2012-01-16 - Version 3.7.10</h3><blockquote> |
| 761 |
SQLite <a href="releaselog/3_7_10.html">version 3.7.10</a> is a regularly scheduled maintenance release. |
| 762 |
Upgrading from version 3.7.6.3, 3.7.7, 3.7.7.1, 3.7.8, or 3.7.9 is |
| 763 |
optional. Upgrading from other releases is recommended.</p> |
| 764 |
|
| 765 |
<p> The <a href="c3ref/c_config_covering_index_scan.html#sqliteconfigpcache">SQLITE_CONFIG_PCACHE</a> mechanism has been replaced with |
| 766 |
<a href="c3ref/c_config_covering_index_scan.html#sqliteconfigpcache2">SQLITE_CONFIG_PCACHE2</a>. If you do not know what this mechanism |
| 767 |
is (it is an extreme corner-case and is seldom used) then this |
| 768 |
change will not effect you in the least.</p> |
| 769 |
|
| 770 |
<p> The default <a href="fileformat2.html#schemaformat">schema format number</a> for new database files has changed |
| 771 |
from 1 to 4. SQLite has been able to generate and read database files |
| 772 |
using schema format 4 for six years. But up unto now, the default |
| 773 |
schema format has been 1 so that older versions of SQLite could read |
| 774 |
and write databases generated by newer versions of SQLite. But those |
| 775 |
older versions of SQLite have become so scarce now that it seems |
| 776 |
reasonable to make the new format the default.</p> |
| 777 |
|
| 778 |
<p> SQLite is changing some of the assumptions it makes above the behavior |
| 779 |
of disk drives and flash memory devices during a sudden power loss. |
| 780 |
This change is completely transparent to applications. |
| 781 |
Read about the <a href="psow.html">powersafe overwrite</a> property for additional information.</p> |
| 782 |
|
| 783 |
<p> Lots of new interfaces have been added in this release: |
| 784 |
<ul> |
| 785 |
<li> <a href="c3ref/db_release_memory.html">sqlite3_db_release_memory()</a> |
| 786 |
<li> <a href="pragma.html#pragma_shrink_memory">PRAGMA shrink_memory</a> |
| 787 |
<li> <a href="c3ref/db_filename.html">sqlite3_db_filename()</a> |
| 788 |
<li> <a href="c3ref/stmt_busy.html">sqlite3_stmt_busy()</a> |
| 789 |
<li> <a href="c3ref/uri_boolean.html">sqlite3_uri_boolean()</a> |
| 790 |
<li> <a href="c3ref/uri_boolean.html">sqlite3_uri_int64()</a> |
| 791 |
</ul></p> |
| 792 |
|
| 793 |
<p> The <a href="pragma.html#pragma_cache_size">PRAGMA cache_size</a> statement has been enhanced. Formerly, you would |
| 794 |
use this statement to tell SQLite how many pages of the database files it |
| 795 |
should hold in its cache at once. The total memory requirement would |
| 796 |
depend on the database page size. Now, if you give <a href="pragma.html#pragma_cache_size">PRAGMA cache_size</a> |
| 797 |
a negative value -N, it will allocate roughly N |
| 798 |
<a href="http://en.wikipedia.org/wiki/Kibibyte">kibibytes</a> of memory to cache, |
| 799 |
divided up according to page size. This enhancement allows programs to |
| 800 |
more easily control their memory usage.</p> |
| 801 |
|
| 802 |
<p> There have been several obscure bug fixes. One noteworthy bug, |
| 803 |
ticket <a href="https://sqlite.org/src/info/ff5be73dee">ff5be73dee</a>, |
| 804 |
could in theory result in a corrupt database file if a power loss |
| 805 |
occurred at just the wrong moment on an unusually cantankerous disk |
| 806 |
drive. But that is mostly a theoretical concern and is very unlikely |
| 807 |
to happen in practice. The bug was found during laboratory testing |
| 808 |
and has never been observed to occur in the wild. |
| 809 |
</blockquote><hr width="50%"><a name="2011_11_01"></a><h3>2011-11-01 - Version 3.7.9</h3><blockquote> |
| 810 |
SQLite <a href="releaselog/3_7_9.html">version 3.7.9</a> is a regularly scheduled maintenance release. |
| 811 |
Upgrading from version 3.7.6.3, 3.7.7, 3.7.7.1, and 3.7.8 is optional. |
| 812 |
Upgrading from other versions is recommended.</p> |
| 813 |
|
| 814 |
<p> The <a href="compile.html#enable_stat2">SQLITE_ENABLE_STAT2</a> compile-time option is now a no-op. The enhanced |
| 815 |
query-planner functionality formerly available using SQLITE_ENABLE_STAT2 |
| 816 |
is now available through <a href="compile.html#enable_stat3">SQLITE_ENABLE_STAT3</a>. The enhanced query planning |
| 817 |
is still disabled by default. However, future releases of SQLite might |
| 818 |
convert STAT3 from an enable-option to a disable-option so that it is |
| 819 |
available by default and is only omitted upon request.</p> |
| 820 |
|
| 821 |
<p> The <a href="fts3.html#fts4">FTS4</a> full-text search engine has been enhanced such that tokens in |
| 822 |
the search string that begin with "^" must be the first token in their |
| 823 |
respective columns in order to match. Formerly, "^" characters in the |
| 824 |
search string were simply ignored. Hence, if a legacy application was |
| 825 |
including "^" characters in FTS4 search strings, thinking that they would |
| 826 |
always be ignored, then those legacy applications might break with this |
| 827 |
update. The fix is simply remove the "^" characters from the search |
| 828 |
string.</p> |
| 829 |
|
| 830 |
<p> See the <a href="releaselog/3_7_9.html">change summary</a> for additional changes associated |
| 831 |
with this release. |
| 832 |
</blockquote><hr width="50%"><a name="2011__eptember_19"></a><h3>2011-September-19 - Version 3.7.8</h3><blockquote> |
| 833 |
SQLite <a href="releaselog/3_7_8.html">version 3.7.8</a> is a quarterly maintenance release. Upgrading from |
| 834 |
versions 3.7.6.3, 3.7.7, or 3.7.7.1 is optional. Upgrading from other |
| 835 |
versions is recommended.</p> |
| 836 |
|
| 837 |
<p> This release features a new "external merge sort" algorithm used to |
| 838 |
implement ORDER BY and GROUP BY and also to presort the content of an |
| 839 |
index for CREATE INDEX. The new algorithm does approximately the same |
| 840 |
number of comparisons and I/Os as before, but the I/Os are much more |
| 841 |
sequential and so runtimes are greatly reduced when the size of the |
| 842 |
set being sorted is larger than the filesystem cache. The performance |
| 843 |
improvement can be dramatic - orders of magnitude faster |
| 844 |
for large CREATE INDEX commands. On the other hand, |
| 845 |
the code is slightly slower (1% or 2%) |
| 846 |
for a small CREATE INDEX. Since CREATE INDEX is not an |
| 847 |
operation that commonly occurs on a speed-critical path, we feel that |
| 848 |
this tradeoff is a good one. The slight slowdown for small CREATE INDEX |
| 849 |
statements might be recovered in a future release. ORDER BY and GROUP BY |
| 850 |
operations should now be faster for all cases, large and small.</p> |
| 851 |
|
| 852 |
<p> The query planner has been enhanced to do a better job of handling |
| 853 |
the DISTINCT keyword on SELECT statements.</p> |
| 854 |
|
| 855 |
<p> There has been a lot of work on the default <a href="vfs.html">VFSes</a>. The Unix VFS has |
| 856 |
been enhanced to include more overrideable system calls - a feature requested |
| 857 |
by Chromium to make it easier to build SQLite into a sandbox. The |
| 858 |
windows VFS has been enhanced to be more resistant to interference from |
| 859 |
anti-virus software.</p> |
| 860 |
|
| 861 |
<p> Every version of SQLite is better tested than the previous, and 3.7.8 |
| 862 |
is no exception to this rule. Version 3.7.8 has been used internally by |
| 863 |
the SQLite team for mission critical functions and has performed flawlessly. |
| 864 |
And, of course, it passes our rigorous <a href="testing.html">testing</a> procedures with no |
| 865 |
problems detected. Version 3.7.8 is recommended for all new development. |
| 866 |
</blockquote><hr width="50%"><a name="2011_06_28"></a><h3>2011-06-28 - Version 3.7.7.1</h3><blockquote> |
| 867 |
SQLite <a href="releaselog/3_7_7_1.html">version 3.7.7.1</a> adds a one-line bug fix to 3.7.7 to fix |
| 868 |
<a href="https://sqlite.org/src/info/25ee812710">a problem</a> |
| 869 |
causing <a href="pragma.html#pragma_case_sensitive_like">PRAGMA case_sensitive_like</a> statements compiled using the legacy |
| 870 |
<a href="c3ref/prepare.html">sqlite3_prepare()</a> interface to fail with an <a href="rescode.html#schema">SQLITE_SCHEMA</a> error. Because |
| 871 |
<a href="c3ref/exec.html">sqlite3_exec()</a> uses sqlite3_prepare() internally, the problem also affects |
| 872 |
sqlite3_exec().</p> |
| 873 |
|
| 874 |
<p> Upgrading from 3.7.7 is only required for applications that use "PRAGMA |
| 875 |
case_sensitive_like" and the sqlite3_prepare() (or sqlite3_exec()) interface. |
| 876 |
</blockquote><hr width="50%"><a name="2011_06_24"></a><h3>2011-06-24 - Version 3.7.7</h3><blockquote> |
| 877 |
SQLite <a href="releaselog/3_7_7.html">version 3.7.7</a> is a regularly scheduled bi-monthly maintenance |
| 878 |
release. Upgrading from version 3.7.6.3 is optional. Upgrading from all |
| 879 |
prior releases is recommended.</p> |
| 880 |
|
| 881 |
<p> This release adds support for naming database files using <a href="uri.html">URI filenames</a>. |
| 882 |
URI filenames are disabled by default (for backwards compatibility) but |
| 883 |
applications are encouraged to enable them since incompatibilities are |
| 884 |
likely to be exceedingly rare and the feature is useful. See the |
| 885 |
<a href="uri.html">URI filename documentation</a> for details.</p> |
| 886 |
|
| 887 |
<p> Most of the other enhancements in this release involve |
| 888 |
<a href="vtab.html">virtual tables</a>. The virtual table interface has been enhanced to |
| 889 |
support <a href="lang_savepoint.html">SAVEPOINT</a> and <a href="lang_conflict.html">ON CONFLICT</a> clause processing, and the built-in |
| 890 |
<a href="rtree.html">RTREE</a> and <a href="fts3.html">FTS3/FTS4</a> have been augmented to take advantage of |
| 891 |
the new capability. This means, for example, that it is now possible |
| 892 |
to use the <a href="lang_replace.html">REPLACE</a> command on <a href="fts3.html">FTS3/FTS4</a> and <a href="rtree.html">RTREE</a> tables.</p> |
| 893 |
|
| 894 |
<p> The <a href="fts3.html#fts4">FTS4</a> full-text index extension has been enhanced to support |
| 895 |
the <a href="fts3.html#fts4prefix">FTS4 prefix option</a> and the <a href="fts3.html#fts4order">FTS4 order option</a>. These two enhancements |
| 896 |
are provided in support of search-as-you-type interfaces where search |
| 897 |
results begin to appear after the first keystroke in the "search" box |
| 898 |
and are refined with each subsequent keystroke. The way this is done is |
| 899 |
to do a separate full-text search after each key stroke, and add the |
| 900 |
"*" wildcard at the end of the word currently being typed. So, for |
| 901 |
example, if the text typed so far is "fast da" and the next character |
| 902 |
typed is "t", then the application does a full-text search of the |
| 903 |
pattern "fast dat*" and displays the results. Such capability has |
| 904 |
always existed. What is new is that the <a href="fts3.html#fts4prefix">FTS4 prefix option</a> allows |
| 905 |
the search to be very fast (a matter of milliseconds) even for difficult |
| 906 |
cases such as "t*" or "th*".</p> |
| 907 |
|
| 908 |
<p> There has been a fair amount of work done on the FTS4 module for this |
| 909 |
release. But the core SQLite code has changed little and the previous |
| 910 |
release has not given any problems, so we expect this to be a very |
| 911 |
stable release. |
| 912 |
</blockquote><hr width="50%"><a name="2011_05_19"></a><h3>2011-05-19 - Version 3.7.6.3</h3><blockquote> |
| 913 |
SQLite <a href="releaselog/3_7_6_3.html">version 3.7.6.3</a> is a patch release that fixes a |
| 914 |
<a href="https://sqlite.org/src/info/2d1a5c67df">single bug</a> |
| 915 |
associated with <a href="wal.html">WAL mode</a>. The bug has been in SQLite ever since WAL |
| 916 |
was added, but the problem is very obscure and so nobody has noticed |
| 917 |
before now. Nevertheless, all users are encouraged to upgrade to |
| 918 |
version 3.7.6.3 or later.</p> |
| 919 |
|
| 920 |
<p> The bug is this: |
| 921 |
If the <a href="pragma.html#pragma_cache_size">cache_size</a> is set very small (less than 10) and SQLite comes |
| 922 |
under memory pressure and if a multi-statement transaction is started |
| 923 |
in which the last statement prior to COMMIT is a SELECT statement and if |
| 924 |
a <a href="wal.html#ckpt">checkpoint</a> occurs right after the transaction commit, then |
| 925 |
it might happen that the transaction will be silently rolled back instead |
| 926 |
of being committed.</p> |
| 927 |
|
| 928 |
<p> The default setting for <a href="pragma.html#pragma_cache_size">cache_size</a> is 2000. So in most situations, this |
| 929 |
bug will never appear. But sometimes programmers set <a href="pragma.html#pragma_cache_size">cache_size</a> to |
| 930 |
very small values on gadgets and other low-memory devices in order to |
| 931 |
save memory space. Such applications are vulnerable. |
| 932 |
Note that this bug does <u>not</u> cause database corruption. It is |
| 933 |
as if <a href="lang_transaction.html">ROLLBACK</a> were being run instead of <a href="lang_transaction.html">COMMIT</a> in some cases.</p> |
| 934 |
|
| 935 |
<p> <b>Bug Details</b></p> |
| 936 |
|
| 937 |
<p> Transactions commit in WAL mode by adding a record onto the end of |
| 938 |
the WAL (the write-ahead log) that contains a "commit" flag. So to |
| 939 |
commit a transaction, SQLite takes all the pages that have changed |
| 940 |
during that transaction, appends them to the WAL, and sets the commit |
| 941 |
flag on the last page. Now, if SQLite comes under memory pressure, it |
| 942 |
might try to free up memory space by writing changed pages to the WAL |
| 943 |
prior to the commit. We call this "spilling" the cache to WAL. There |
| 944 |
is nothing wrong with spilling cache to WAL. But if the |
| 945 |
memory pressure is severe, it might be that by the time <a href="lang_transaction.html">COMMIT</a> is run, |
| 946 |
all changed pages for the transaction have already been spilled to WAL |
| 947 |
and there are no pages left to be written to WAL. |
| 948 |
And with no unwritten pages, there was nothing to put the commit flag |
| 949 |
on. And without a commit flag, the transaction would end up being |
| 950 |
rolled back.</p> |
| 951 |
|
| 952 |
<p> The fix to this problem was that if all changed pages has already |
| 953 |
been written to the WAL when the commit was started, then page 1 of |
| 954 |
the database will be written to the WAL again, so that there will always |
| 955 |
be a page available on which to set the commit flag. |
| 956 |
</blockquote><hr width="50%"><a name="2011_04_17"></a><h3>2011-04-17 - Version 3.7.6.2</h3><blockquote> |
| 957 |
SQLite <a href="releaselog/3_7_6_2.html">version 3.7.6.2</a> adds a one-line bug fix to 3.7.6.1 that enables |
| 958 |
pthreads to work correctly on NetBSD. The problem was a faulty function |
| 959 |
signature for the open system call. The problem does not appear to have |
| 960 |
any adverse impact on any system other than NetBSD.</p> |
| 961 |
|
| 962 |
<p> Upgrading from version 3.7.6.1 is only needed on NetBSD. |
| 963 |
</blockquote><hr width="50%"><a name="2011_04_13"></a><h3>2011-04-13 - Version 3.7.6.1</h3><blockquote> |
| 964 |
SQLite <a href="releaselog/3_7_6_1.html">version 3.7.6.1</a> fixes a single bug in 3.7.6 that can cause a |
| 965 |
segfault if <a href="c3ref/c_fcntl_begin_atomic_write.html#sqlitefcntlsizehint">SQLITE_FCNTL_SIZE_HINT</a> is used on a Unix build that has |
| 966 |
SQLITE_ENABLE_LOCKING_MODE set to 0 and is compiled with |
| 967 |
HAVE_POSIX_FALLOCATE.</p> |
| 968 |
|
| 969 |
<p> Upgrading from 3.7.6 is only needed for users effected by the |
| 970 |
configuration-specific bug described above. There are no other changes |
| 971 |
to the code. |
| 972 |
</blockquote><hr width="50%"><a name="2011_04_12"></a><h3>2011-04-12 - Version 3.7.6</h3><blockquote> |
| 973 |
SQLite <a href="releaselog/3_7_6.html">version 3.7.6</a> is a regularly scheduled bi-monthly maintenance |
| 974 |
release of SQLite. Upgrading from version 3.7.5 is optional. Upgrading |
| 975 |
releases prior to 3.7.5 is recommended. |
| 976 |
</blockquote><hr width="50%"><a name="2011_02_01"></a><h3>2011-02-01 - Version 3.7.5</h3><blockquote> |
| 977 |
SQLite <a href="releaselog/3_7_5.html">version 3.7.5</a> is a regularly scheduled bi-monthly maintenance |
| 978 |
release of SQLite. Due to the discovery and fix of |
| 979 |
<a href="https://sqlite.org/src/tktview?name=5d863f876e">an obscure bug</a> |
| 980 |
that could cause database corruption, upgrading from all prior |
| 981 |
releases of SQLite is recommended. This bug was found during code |
| 982 |
review and has not been observed in the wild.</p> |
| 983 |
|
| 984 |
<p> This release adds new <a href="c3ref/c_dbstatus_options.html#sqlitedbstatuslookasidehit">opcodes</a> for the |
| 985 |
<a href="c3ref/db_status.html">sqlite3_db_status()</a> interface that allow more precise measurement of |
| 986 |
how the <a href="malloc.html#lookaside">lookaside memory allocator</a> is performing, which can be useful |
| 987 |
for tuning in applications with very tight memory constraints.</p> |
| 988 |
|
| 989 |
<p> The <a href="c3ref/mprintf.html">sqlite3_vsnprintf()</a> interface was added. This routine is simply |
| 990 |
a varargs version of the long-standing <a href="c3ref/mprintf.html">sqlite3_snprintf()</a> interface.</p> |
| 991 |
|
| 992 |
<p> The output from <a href="c3ref/profile.html">sqlite3_trace()</a> interface has been enhanced to work |
| 993 |
better (and faster) in systems that use recursive extensions such as |
| 994 |
<a href="fts3.html">FTS3</a> or <a href="rtree.html">RTREE</a>.</p> |
| 995 |
|
| 996 |
<p> Testing with Valgrind shows that this release of SQLite is about 1% |
| 997 |
or 2% faster than the previous release for most operations.</p> |
| 998 |
|
| 999 |
<p> A fork of the popular ADO.NET adaptor for SQLite known as System.Data.SQLite |
| 1000 |
is now available on <a href="http://System.Data.SQLite.org/">http://System.Data.SQLite.org/</a>. The originator |
| 1001 |
of System.Data.SQLite, Robert Simpson, is aware of this fork, has |
| 1002 |
expressed his approval, and has commit privileges on the new Fossil |
| 1003 |
repository. The SQLite development team intends to maintain |
| 1004 |
System.Data.SQLite moving forward. |
| 1005 |
</blockquote><hr width="50%"><a name="2010_12_08"></a><h3>2010-12-08 - Version 3.7.4</h3><blockquote> |
| 1006 |
SQLite <a href="releaselog/3_7_4.html">version 3.7.4</a> is a regularly scheduled bi-monthly maintenance |
| 1007 |
release of SQLite. Upgrading from <a href="releaselog/3_7_2.html">version 3.7.2</a> and <a href="releaselog/3_7_3.html">version 3.7.3</a> |
| 1008 |
is optional. Upgrading from all other SQLite releases is recommended.</p> |
| 1009 |
|
| 1010 |
<p> This release features <a href="fts3.html">full-text search</a> enhancements. The older |
| 1011 |
<a href="fts3.html">FTS3</a> virtual table is still fully supported, and should also run |
| 1012 |
faster. In addition, the new <a href="fts3.html#fts4">FTS4</a> virtual table is added. FTS4 |
| 1013 |
follows the same syntax as FTS3 but holds additional metadata which |
| 1014 |
facilitates some performance improvements and more advanced |
| 1015 |
<a href="fts3.html#matchinfo">matchinfo()</a> output. Look for further full-text search enhancements |
| 1016 |
in subsequent releases.</p> |
| 1017 |
|
| 1018 |
<p> Also in this release, the <a href="eqp.html">EXPLAIN QUERY PLAN</a> output has been enhanced |
| 1019 |
and new documentation is provided so that application developers can |
| 1020 |
more easily understand how SQLite is performing their queries.</p> |
| 1021 |
|
| 1022 |
<p> Thanks to an account from the folks at <a href="http://www.devio.us/">http://www.devio.us/</a>, OpenBSD |
| 1023 |
has been added to the list of platforms upon which we |
| 1024 |
<a href="testing.html">test SQLite</a> prior to every release. That list of platforms |
| 1025 |
now includes:</p> |
| 1026 |
|
| 1027 |
<p> <ul> |
| 1028 |
<li> Linux x86 & x86_64 |
| 1029 |
<li> MacOS 10.5 & 10.6 |
| 1030 |
<li> MacOS 10.2 PowerPC |
| 1031 |
<li> WinXP and Win7 |
| 1032 |
<li> Android 2.2 |
| 1033 |
<li> OpenBSD 4.7 |
| 1034 |
</ul></p> |
| 1035 |
|
| 1036 |
<p> The previous release of SQLite (<a href="releaselog/3_7_3.html">version 3.7.3</a>) has proven to be very |
| 1037 |
robust. The only serious issue discovered was |
| 1038 |
<a href="https://sqlite.org/src/info/80ba201079">ticket 80ba201079</a> that |
| 1039 |
describes an incorrect query result that can occur under very |
| 1040 |
unusual circumstances. The ticket description contains details of the |
| 1041 |
problem. Suffice it to say here that the problem is very obscure and |
| 1042 |
is unlikely to effect most applications and so upgrading is optional. |
| 1043 |
The problem is fixed, of course, in this release. |
| 1044 |
</blockquote><hr width="50%"><a name="2010__ctober_08"></a><h3>2010-October-08 - Version 3.7.3</h3><blockquote> |
| 1045 |
SQLite <a href="releaselog/3_7_3.html">version 3.7.3</a> is a regularly scheduled bi-monthly maintenance |
| 1046 |
release of SQLite. Upgrading from <a href="releaselog/3_7_2.html">version 3.7.2</a> is optional. |
| 1047 |
Upgrading from all other releases is recommended.</p> |
| 1048 |
|
| 1049 |
<p> This release adds two new interfaces (really just variations on existing |
| 1050 |
interfaces). The <a href="c3ref/create_function.html">sqlite3_create_function_v2()</a> interface adds a |
| 1051 |
destructor for the application-data pointer. The new |
| 1052 |
<a href="c3ref/hard_heap_limit64.html">sqlite3_soft_heap_limit64()</a> interface allows the soft heap limit to |
| 1053 |
be set to a value greater than 2<sup>31</sup>.</p> |
| 1054 |
|
| 1055 |
<p> The <a href="rtree.html">RTREE</a> extension has been enhanced with the ability to have an |
| 1056 |
<a href="rtree.html#customquery">application-defined query region</a>. This might |
| 1057 |
be used, for example, to locate all objects within |
| 1058 |
the field of view of a camera.</p> |
| 1059 |
|
| 1060 |
<p> The 3.7.3 release also includes some performance enhancements, including |
| 1061 |
query planner improvements, documentation updates, |
| 1062 |
and fixes to some very obscure bugs. |
| 1063 |
</blockquote><hr width="50%"><a name="2010__ugust_24"></a><h3>2010-August-24 - Version 3.7.2</h3><blockquote> |
| 1064 |
SQLite <a href="releaselog/3_7_2.html">version 3.7.2</a> fixes a long-standing bug that can cause the |
| 1065 |
database <a href="fileformat2.html#freelist">free-page list</a> to go corrupt if <a href="pragma.html#pragma_incremental_vacuum">incremental_vacuum</a> is used |
| 1066 |
multiple times to |
| 1067 |
partially reduce the size of a database file that contains many hundreds |
| 1068 |
of unused database pages. The original bug reports together with links |
| 1069 |
to the patch that fixes it can be seen |
| 1070 |
<a href="https://sqlite.org/src/info/5e10420e8d">here</a>.</p> |
| 1071 |
|
| 1072 |
<p> This bug has been in the code for at least a year and possibly longer. |
| 1073 |
The bug has nothing to do with the versions 3.7.1 or 3.7.0 or any other |
| 1074 |
recent release. The fact that the bug was discovered (and fixed) |
| 1075 |
within hours of the 3.7.1 release is purely a coincidence.</p> |
| 1076 |
|
| 1077 |
<p> The bug is impossible to hit without using <a href="pragma.html#pragma_incremental_vacuum">incremental_vacuum</a> and is |
| 1078 |
very difficult to hit even with incremental_vacuum. And the kind of |
| 1079 |
corruption that the bug causes can usually be fixed |
| 1080 |
simply by running <a href="lang_vacuum.html">VACUUM</a>. Nevertheless, because the bug can result |
| 1081 |
in database corruption, it is recommended that all SQLite users upgrade |
| 1082 |
to version 3.7.2 or later. |
| 1083 |
</blockquote><hr width="50%"><a name="2010__ugust_23"></a><h3>2010-August-23 - Version 3.7.1</h3><blockquote> |
| 1084 |
SQLite <a href="releaselog/3_7_1.html">version 3.7.1</a> is a stabilization release for the 3.7.x series. |
| 1085 |
Other than the filesize-in-header bug that was fixed in <a href="releaselog/3_7_0_1.html">version 3.7.0.1</a>, |
| 1086 |
no major problems have been seen in 3.7.0. Some minor corner-case |
| 1087 |
performance regressions have been fixed. A typo in the OS/2 interface |
| 1088 |
has been repaired.</p> |
| 1089 |
|
| 1090 |
<p> A biggest part of the 3.7.1 release is a cleanup and refactoring of |
| 1091 |
the pager module within SQLite. This refactoring should have no |
| 1092 |
application-visible effects. The purpose was to reorganize the code |
| 1093 |
in ways that make it easier to prove correctness.</p> |
| 1094 |
|
| 1095 |
<p> The 3.7.1 release adds new experimental methods for obtained more |
| 1096 |
detailed memory usage information and for controlling database file |
| 1097 |
fragmentation. And the query planner now does a better job of |
| 1098 |
optimizing the <a href="lang_expr.html#like">LIKE</a> and <a href="lang_expr.html#glob">GLOB</a> operators.</p> |
| 1099 |
|
| 1100 |
<p> This release increases the maximum size of database pages from 32KiB to |
| 1101 |
64KiB. A database with 64KiB pages will not be readable or writable by |
| 1102 |
older versions of SQLite. Note that further increases in page size |
| 1103 |
are not feasible since the <a href="fileformat2.html">file format</a> uses 16-bit offsets to structures |
| 1104 |
within each page. |
| 1105 |
</blockquote><hr width="50%"><a name="2010__ugust_04"></a><h3>2010-August-04 - Version 3.7.0.1</h3><blockquote> |
| 1106 |
SQLite <a href="releaselog/3_7_0_1.html">version 3.7.0.1</a> is a patch release to fix a bug in the new |
| 1107 |
filesize-in-header feature of the <a href="fileformat2.html">SQLite file format</a> |
| 1108 |
that could cause database corruption if the same database file is |
| 1109 |
written alternately with version 3.7.0 and version 3.6.23.1 or earlier. |
| 1110 |
A performance regression was also fixed in this release. |
| 1111 |
</blockquote><hr width="50%"><a name="2010_07_22"></a><h3>2010-07-22 - Version 3.7.0</h3><blockquote> |
| 1112 |
SQLite <a href="releaselog/3_7_0.html">version 3.7.0</a> is a major release of SQLite that features |
| 1113 |
a new transaction control mechanism using a <a href="wal.html">write-ahead log</a> or <a href="wal.html">WAL</a>. |
| 1114 |
The traditional rollback-journal is still used as the default so there |
| 1115 |
should be no visible change for legacy programs. But newer programs |
| 1116 |
can take advantage of improved performance and concurrency by enabling |
| 1117 |
the WAL journaling mode.</p> |
| 1118 |
|
| 1119 |
<p> SQLite version 3.7.0 also contains some query planner enhancements and |
| 1120 |
a few obscure bug fixes, but the only really big change is the addition |
| 1121 |
of WAL mode. |
| 1122 |
</blockquote><hr width="50%"><a name="2010_03_30"></a><h3>2010-03-30 - Version 3.6.23.1</h3><blockquote> |
| 1123 |
SQLite <a href="releaselog/3_6_23_1.html">version 3.6.23.1</a> is a patch release to fix a bug in the |
| 1124 |
offsets() function of <a href="fts3.html">FTS3</a> at the request of the Mozilla. |
| 1125 |
</blockquote><hr width="50%"><a name="2010_03_09"></a><h3>2010-03-09 - Version 3.6.23</h3><blockquote> |
| 1126 |
SQLite <a href="releaselog/3_6_23.html">version 3.6.23</a> is a regular bimonthly release of SQLite. |
| 1127 |
Upgrading from the prior release is purely optional.</p> |
| 1128 |
|
| 1129 |
<p> This release contains new pragmas: the <a href="pragma.html#pragma_secure_delete">secure_delete pragma</a>, and |
| 1130 |
the <a href="pragma.html#pragma_compile_options">compile_options pragma</a>. |
| 1131 |
There are a new SQL functions: <a href="lang_corefunc.html#sqlite_compileoption_used">sqlite_compileoption_used()</a> |
| 1132 |
and <a href="lang_corefunc.html#sqlite_compileoption_get">sqlite_compileoption_get()</a>. |
| 1133 |
New C/C++ interfaces: <a href="c3ref/compileoption_get.html">sqlite3_compileoption_used()</a>, |
| 1134 |
<a href="c3ref/compileoption_get.html">sqlite3_compileoption_get()</a>, <a href="c3ref/c_config_covering_index_scan.html#sqliteconfiglog">SQLITE_CONFIG_LOG</a>, and |
| 1135 |
<a href="c3ref/log.html">sqlite3_log()</a>.</p> |
| 1136 |
|
| 1137 |
<p> This release also includes several minor bug fixes and performance |
| 1138 |
improvements. Support for <a href="compile.html#omit_floating_point">SQLITE_OMIT_FLOATING_POINT</a> is enhanced. |
| 1139 |
There are on-going improvements to <a href="fts3.html">FTS3</a>.</p> |
| 1140 |
|
| 1141 |
<p> The ".genfkey" command in the <a href="cli.html">Command Line Interface</a> has been |
| 1142 |
removed. SQLite has supported standard SQL <a href="foreignkeys.html">foreign key constraints</a> |
| 1143 |
since <a href="releaselog/3_6_19.html">version 3.6.19</a> and so the ".genfkey" command was seen as |
| 1144 |
an anachronism. |
| 1145 |
</blockquote><hr width="50%"><a name="2010_01_06"></a><h3>2010-01-06 - Version 3.6.22</h3><blockquote> |
| 1146 |
SQLite <a href="releaselog/3_6_22.html">version 3.6.22</a> is a bug-fix release. Two bugs have been fixed |
| 1147 |
that might cause incorrect query results. |
| 1148 |
<ul> |
| 1149 |
<li>Ticket <a href="https://sqlite.org/src/info/31338dca7e">31338dca7e</a> |
| 1150 |
describes a |
| 1151 |
problem with queries that have a WHERE clause of the form (x AND y) OR z |
| 1152 |
where x and z come from one table of a join and y comes from a different |
| 1153 |
table. |
| 1154 |
<li> Ticket <a href="https://sqlite.org/src/info/eb5548a849">eb5548a849</a> |
| 1155 |
describes |
| 1156 |
a problem where the use of the CAST operator in the WHERE clause can lead |
| 1157 |
to incorrect results if the column being cast to a new datatype is also |
| 1158 |
used in the same WHERE clause without being cast. |
| 1159 |
</ul> |
| 1160 |
Both bugs are obscure, |
| 1161 |
but because they could arise in an application after deployment, it is |
| 1162 |
recommended that all applications upgrade SQLite to version 3.6.22.</p> |
| 1163 |
|
| 1164 |
<p> This release also includes other minor bug fixes and performance |
| 1165 |
enhancements, especially in the <a href="fts3.html">FTS3</a> extension. |
| 1166 |
</blockquote><hr width="50%"><a name="2009_12_07"></a><h3>2009-12-07 - Version 3.6.21</h3><blockquote> |
| 1167 |
SQLite <a href="releaselog/3_6_21.html">version 3.6.21</a> focuses on performance optimization. For |
| 1168 |
a certain set of traces, this version uses 12% fewer CPU instructions |
| 1169 |
than the previous release (as measured by Valgrind). In addition, the |
| 1170 |
<a href="fts3.html">FTS3</a> extension has been through an extensive cleanup and rework and |
| 1171 |
the <a href="c3ref/profile.html">sqlite3_trace()</a> interface has been modified to insert |
| 1172 |
<a href="lang_expr.html#varparam">bound parameter</a> values into its output. |
| 1173 |
</blockquote><hr width="50%"><a name="2009_11_04"></a><h3>2009-11-04 - Version 3.6.20</h3><blockquote> |
| 1174 |
SQLite <a href="releaselog/3_6_20.html">version 3.6.20</a> is a general maintenance release. The |
| 1175 |
query planner has been enhanced to work better with bound parameters |
| 1176 |
in LIKE and GLOB operators and in range constraints and various minor |
| 1177 |
bugs have been fixed. Upgrading from 3.6.19 is optional. |
| 1178 |
</blockquote><hr width="50%"><a name="2009_10_14"></a><h3>2009-10-14 - Version 3.6.19</h3><blockquote> |
| 1179 |
SQLite <a href="releaselog/3_6_19.html">version 3.6.19</a> adds native support for |
| 1180 |
<a href="foreignkeys.html">foreign key constraints</a>, including deferred constraints and |
| 1181 |
cascading deletes. Enforcement of foreign keys is disabled by |
| 1182 |
default for backwards compatibility and must be turned on using |
| 1183 |
the <a href="pragma.html#pragma_foreign_keys">foreign_keys pragma</a>.</p> |
| 1184 |
|
| 1185 |
<p> Version 3.6.19 also adds support for the |
| 1186 |
<a href="lang_expr.html#isisnot">IS and IS NOT operators</a>. Formerly, SQLite (as most |
| 1187 |
other SQL database engines) supported IS NULL and IS NOT NULL. The |
| 1188 |
IS and IS NOT operators are generalizations that allow the right-hand |
| 1189 |
side to be an arbitrary expression. IS and IS NOT work the same as |
| 1190 |
== (equals) and != (not equals) except that with IS and IS NOT the |
| 1191 |
NULL values compare equal to one another. |
| 1192 |
</blockquote><hr width="50%"><a name="2009_09_11"></a><h3>2009-09-11 - Version 3.6.18</h3><blockquote> |
| 1193 |
Beginning with this release, the SQLite source code is tracked and |
| 1194 |
managed using the <a href="http://www.fossil-scm.org/">Fossil</a> |
| 1195 |
distributed configuration management system. SQLite was previously |
| 1196 |
versioned using CVS. The entire CVS history has been imported into |
| 1197 |
Fossil. The older CVS repository remains on the website but is |
| 1198 |
read-only.</p> |
| 1199 |
|
| 1200 |
<p> There are two major enhancements in SQLite version 3.6.18. The first |
| 1201 |
is a series or refinements to the query planner that help SQLite to |
| 1202 |
choose better plans for joins where in the past it was selecting suboptimal |
| 1203 |
query plans. The <a href="compile.html#enable_stat2">SQLITE_ENABLE_STAT2</a> compile-time option has been |
| 1204 |
added to cause SQLite to collect histogram data on indices when the |
| 1205 |
<a href="lang_analyze.html">ANALYZE</a> command is run. The use of histograms improve the query |
| 1206 |
planning performance even more.</p> |
| 1207 |
|
| 1208 |
<p> The second major enhancement is that SQLite now support recursive |
| 1209 |
triggers. The older non-recursive behavior of triggers is still the |
| 1210 |
default behavior. Recursive triggers are activated using the |
| 1211 |
<a href="pragma.html#pragma_recursive_triggers">recursive_triggers pragma</a>. In addition to allowing triggers to |
| 1212 |
call themselves (either directly or indirectly) the new capability |
| 1213 |
also fires DELETE triggers on rows that are removed from a table |
| 1214 |
as a result of <a href="lang_conflict.html">REPLACE</a> conflict resolution processing.</p> |
| 1215 |
|
| 1216 |
<p> Non-recursive triggers are still the default behavior since this |
| 1217 |
is least likely to cause problems for existing applications. However, |
| 1218 |
we anticipate that triggers will become |
| 1219 |
recursive by default beginning with release 3.7.0. At that point, |
| 1220 |
applications that want to continue using the older non-recursive |
| 1221 |
trigger behavior will need to use the <a href="pragma.html#pragma_recursive_triggers">recursive_triggers pragma</a> |
| 1222 |
to disable recursive triggers.</p> |
| 1223 |
|
| 1224 |
<p> This version of SQLite also contains bug fixes, though none of the |
| 1225 |
bugs are serious and all are obscure, so upgrading is optional.</p> |
| 1226 |
|
| 1227 |
<p> The SQLite core continues to have <a href="testing.html#coverage">100% branch test coverage</a> |
| 1228 |
and so despite the many changes in this release, the developers |
| 1229 |
believe that this version of SQLite is stable and ready for production |
| 1230 |
use. |
| 1231 |
</blockquote><hr width="50%"><a name="2009_08_10"></a><h3>2009-08-10 - Version 3.6.17</h3><blockquote> |
| 1232 |
This is a monthly maintenance release with a focus of bug fixes, |
| 1233 |
performance improvements, and increased test coverage. This is the |
| 1234 |
first release of SQLite since <a href="testing.html#coverage">100% branch test coverage</a> |
| 1235 |
was achieved on the SQLite core.</p> |
| 1236 |
|
| 1237 |
<p> In addition, a new interface <a href="c3ref/stricmp.html">sqlite3_strnicmp()</a> is provided for the |
| 1238 |
convenience of extension writers.</p> |
| 1239 |
|
| 1240 |
<p> None of the bugs fixed in this release are serious. All bugs are |
| 1241 |
obscure. Upgrading is optional. |
| 1242 |
</blockquote><hr width="50%"><a name="2009_07_25"></a><h3>2009-07-25 - 100% Branch Test Coverage</h3><blockquote> |
| 1243 |
A subset of the <a href="th3.html">TH3</a> test suite was measured by gcov to provide |
| 1244 |
<a href="testing.html#coverage">100% branch test coverage</a> over the SQLite core |
| 1245 |
(exclusive of the VFS backend and of extensions such as FTS3 and RTREE) |
| 1246 |
when compiled for SuSE 10.1 Linux on x86. The SQLite developers pledge |
| 1247 |
to maintain branch test coverage at 100% in all future releases. |
| 1248 |
Ongoing work will strive for 100% branch test coverage on the |
| 1249 |
operating-system backends and extensions as well. |
| 1250 |
</blockquote><hr width="50%"><a name="2009_06_27"></a><h3>2009-06-27 - Version 3.6.16</h3><blockquote> |
| 1251 |
SQLite <a href="releaselog/3_6_16.html">version 3.6.16</a> is another general maintenance release containing |
| 1252 |
performance and robustness enhancements. A single notable bug was fixed |
| 1253 |
(ticket #3929). This bug can cause INSERT or UPDATE statements to fail |
| 1254 |
on indexed tables that have AFTER triggers that modify the same table and |
| 1255 |
index. |
| 1256 |
</blockquote><hr width="50%"><a name="2009_06_15"></a><h3>2009-06-15 - Version 3.6.15</h3><blockquote> |
| 1257 |
SQLite <a href="releaselog/3_6_15.html">version 3.6.15</a> is a general maintenance release containing |
| 1258 |
performance and robustness enhancements and fixes for various obscure |
| 1259 |
bugs. |
| 1260 |
</blockquote><hr width="50%"><a name="2009_05_25"></a><h3>2009-05-25 - Version 3.6.14.2</h3><blockquote> |
| 1261 |
SQLite <a href="releaselog/3_6_14_2.html">version 3.6.14.2</a> fixes an obscure bug in the code generator |
| 1262 |
(ticket #3879) |
| 1263 |
section of SQLite which can potentially cause incorrect query results. |
| 1264 |
The changes from the prior release consist of only this one bug fix, |
| 1265 |
check-in [6676] |
| 1266 |
and a change to the version number text.</p> |
| 1267 |
|
| 1268 |
<p> The bug was introduced in version 3.6.14. It is recommended that |
| 1269 |
users of version 3.6.14 and 3.6.14.1 upgrade to this release. Applications |
| 1270 |
are unlikely to hit this bug, but since it is difficult to predict which |
| 1271 |
applications might hit it and which might not, we recommend that all |
| 1272 |
users of 3.6.14 and 3.5.14.1 upgrade to this release. |
| 1273 |
</blockquote><hr width="50%"><a name="2009_05_19"></a><h3>2009-05-19 - Version 3.6.14.1</h3><blockquote> |
| 1274 |
SQLite <a href="releaselog/3_6_14_1.html">version 3.6.14.1</a> is a patch release to <a href="releaselog/3_6_14.html">version 3.6.14</a> with |
| 1275 |
minimal changes that fixes three bugs. Upgrading is only necessary |
| 1276 |
for users who are impacted by one or more of those bugs. |
| 1277 |
</blockquote><hr width="50%"><a name="2009_05_07"></a><h3>2009-05-07 - Version 3.6.14</h3><blockquote> |
| 1278 |
SQLite <a href="releaselog/3_6_14.html">version 3.6.14</a> provides new performance enhancements in |
| 1279 |
the btree and pager layers and in the query optimizer. Certain |
| 1280 |
workloads can be as much as twice as fast as the previous release, |
| 1281 |
though 10% faster is a more typical result.</p> |
| 1282 |
|
| 1283 |
<p> Queries against <a href="vtab.html">virtual tables</a> that contain OR and IN operators |
| 1284 |
in the WHERE clause are now able to use indexing.</p> |
| 1285 |
|
| 1286 |
<p> A new optional asynchronous I/O backend is available for |
| 1287 |
Unix and Windows. The asynchronous backend gives the illusion of faster |
| 1288 |
response time by pushing slow write operations into a background thread. |
| 1289 |
The tradeoff for faster response time is that more memory is required |
| 1290 |
(to hold the content of the pending writes) and if a power failure or |
| 1291 |
program crash occurs, some transactions that appeared to have committed |
| 1292 |
might end up being rolled back upon restart.</p> |
| 1293 |
|
| 1294 |
<p> This release also contains many minor bug fixes, documentation enhancements, |
| 1295 |
new test cases, and cleanups and simplifications to the source code.</p> |
| 1296 |
|
| 1297 |
<p> There is no compelling reason to upgrade from versions 3.6.12 or |
| 1298 |
3.6.13 if those prior versions are working. Though many users may |
| 1299 |
benefit from the improved performance. |
| 1300 |
</blockquote><hr width="50%"><a name="2008_12_16"></a><h3>2008-12-16 - Version 3.6.7</h3><blockquote> |
| 1301 |
SQLite <a href="releaselog/3_6_7.html">version 3.6.7</a> contains a major cleanup of the Unix driver, |
| 1302 |
and support for the new Proxy Locking mechanism on Mac OS X. Though |
| 1303 |
the Unix driver is reorganized, its functionality is the same and so |
| 1304 |
applications should not notice a difference. |
| 1305 |
</blockquote><hr width="50%"><a name="2008_11_26"></a><h3>2008-11-26 - Version 3.6.6.2</h3><blockquote> |
| 1306 |
This release fixes a bug that was introduced into SQLite <a href="releaselog/3_6_6.html">version 3.6.6</a> |
| 1307 |
and which seems like it might be able to cause database corruption. This |
| 1308 |
bug was detected during stress testing. It has not been seen in the wild. |
| 1309 |
An analysis of the problem suggests that the bug might be able to cause |
| 1310 |
database corruption, however focused efforts to find a real-world test |
| 1311 |
cases that actually causes database corruption have so far been unsuccessful. |
| 1312 |
Hence, the likelihood of this bug causing problems is low. Nevertheless, |
| 1313 |
we have decided to do an emergency branch release out of an abundance of |
| 1314 |
caution.</p> |
| 1315 |
|
| 1316 |
<p> The <a href="releaselog/3_6_6_2.html">version 3.6.6.2</a> release also fixes an obscure memory leak that |
| 1317 |
can occur following a disk I/O error. |
| 1318 |
</blockquote><hr width="50%"><a name="2008_11_22"></a><h3>2008-11-22 - Version 3.6.6.1</h3><blockquote> |
| 1319 |
This release fixes a bug that was introduced into SQLite <a href="releaselog/3_6_4.html">version 3.6.4</a> |
| 1320 |
and that can cause database corruption in obscure cases. This bug has |
| 1321 |
never been seen in the wild; it was first detected by internal stress |
| 1322 |
tests and required substantial analysis before it could be shown to |
| 1323 |
potentially lead to corruption. So we feel that SQLite versions 3.6.4, |
| 1324 |
3.6.5, and 3.6.6 are safe to use for development work. But upgrading |
| 1325 |
to this patch release or later is recommended prior to deploying |
| 1326 |
products that incorporate SQLite.</p> |
| 1327 |
|
| 1328 |
<p> We have taken the unusual step of issuing a patch release in order to |
| 1329 |
get the fix for this bug into circulation quickly. SQLite version 3.6.7 |
| 1330 |
will continue on its normal path of development with an anticipated |
| 1331 |
release in mid December. |
| 1332 |
</blockquote><hr width="50%"><a name="2008_11_19"></a><h3>2008-11-19 - Version 3.6.6</h3><blockquote> |
| 1333 |
SQLite <a href="releaselog/3_6_5.html">version 3.6.5</a> is released. This is a quick turn-around release |
| 1334 |
that fixes a bug in virtual tables and FTS3 that snuck into |
| 1335 |
<a href="releaselog/3_6_5.html">version 3.6.5</a>. This release also adds the new |
| 1336 |
application-defined page cache mechanism. |
| 1337 |
</blockquote><hr width="50%"><a name="2008_11_12"></a><h3>2008-11-12 - Version 3.6.5</h3><blockquote> |
| 1338 |
SQLite <a href="releaselog/3_6_5.html">version 3.6.5</a> is released. There are various minor feature |
| 1339 |
enhancements and numerous obscure bug fixes. |
| 1340 |
The <a href="releaselog/3_6_5.html">change log</a> contains the details. Upgrading is |
| 1341 |
optional. |
| 1342 |
</blockquote><hr width="50%"><a name="2008_11_01"></a><h3>2008-11-01 - Bloomberg Joins SQLite Consortium</h3><blockquote> |
| 1343 |
The SQLite developers are honored to announce that |
| 1344 |
<a href="http://www.bloomberg.com/">Bloomberg</a> has joined the |
| 1345 |
<a href="consortium.html">SQLite Consortium</a>. |
| 1346 |
</blockquote><hr width="50%"><a name="2008_10_15"></a><h3>2008-10-15 - Version 3.6.4</h3><blockquote> |
| 1347 |
SQLite version 3.6.4 adds new features designed to help applications |
| 1348 |
detect when indices are not being used on query. There are also some |
| 1349 |
important performance improvements. Upgrading is optional. |
| 1350 |
</blockquote><hr width="50%"><a name="2008_09_22"></a><h3>2008-09-22 - Version 3.6.3</h3><blockquote> |
| 1351 |
SQLite version 3.6.3 fixes a bug in SELECT DISTINCT that was introduced |
| 1352 |
by the previous version. No new features are added. Upgrading is |
| 1353 |
recommended for all applications that make use of DISTINCT. |
| 1354 |
</blockquote><hr width="50%"><a name="2008_08_30"></a><h3>2008-08-30 - Version 3.6.2</h3><blockquote> |
| 1355 |
SQLite version 3.6.2 contains rewrites of the page-cache subsystem and |
| 1356 |
the procedures for matching identifiers to table columns in SQL statements. |
| 1357 |
These changes are designed to better modularize the code and make it more |
| 1358 |
maintainable and reliable moving forward. Nearly 5000 non-comment lines |
| 1359 |
of core code (about 11.3%) have changed |
| 1360 |
from the previous release. Nevertheless, there should be no |
| 1361 |
application-visible changes, other than bug fixes. |
| 1362 |
</blockquote><hr width="50%"><a name="2008_08_06"></a><h3>2008-08-06 - Version 3.6.1</h3><blockquote> |
| 1363 |
SQLite version 3.6.1 is a stabilization and performance enhancement |
| 1364 |
release. |
| 1365 |
</blockquote><hr width="50%"><a name="2008_07_16"></a><h3>2008-07-16 - Version 3.6.0 beta</h3><blockquote> |
| 1366 |
Version 3.6.0 makes changes to the <a href="c3ref/vfs.html">VFS</a> object in order |
| 1367 |
to make SQLite more easily portable to a wider variety of platforms. |
| 1368 |
There are potential incompatibilities with some legacy applications. |
| 1369 |
See the <a href="35to36.html">35to36.html</a> document for details.</p> |
| 1370 |
|
| 1371 |
<p> Many new interfaces are introduced in version 3.6.0. The code is |
| 1372 |
very well tested and is appropriate for use in stable systems. We |
| 1373 |
have attached the "beta" designation only so that we can make tweaks to |
| 1374 |
the new interfaces in the next release without having to declare an |
| 1375 |
incompatibility. |
| 1376 |
</blockquote><hr width="50%"><a name="2008_05_12"></a><h3>2008-05-12 - Version 3.5.9</h3><blockquote> |
| 1377 |
Version 3.5.9 adds a new experimental <a href="pragma.html#syntax">PRAGMA</a>: <a href="pragma.html#pragma_journal_mode">journal_mode</a>. |
| 1378 |
Setting the journal mode to PERSIST can provide performance improvement |
| 1379 |
on systems where deleting a file is expensive. The PERSIST journal |
| 1380 |
mode is still considered experimental and should be used with caution |
| 1381 |
pending further testing.</p> |
| 1382 |
|
| 1383 |
<p> Version 3.5.9 is intended to be the last stable release prior to |
| 1384 |
version 3.6.0. Version 3.6.0 will make incompatible changes to the |
| 1385 |
<a href="c3ref/vfs.html">sqlite3_vfs</a> VFS layer in order to address deficiencies in the original |
| 1386 |
design. These incompatibilities will only effect programmers who |
| 1387 |
write their own custom VFS layers (typically embedded device builders). |
| 1388 |
The planned VFS changes will be much smaller |
| 1389 |
than the changes that occurred on the |
| 1390 |
<a href="34to35.html">3.4.2 to 3.5.0 transaction</a> that occurred last |
| 1391 |
September.</p> |
| 1392 |
|
| 1393 |
<p> This release of SQLite is considered stable and ready for production use. |
| 1394 |
</blockquote><hr width="50%"><a name="2008_04_16"></a><h3>2008-04-16 - Version 3.5.8</h3><blockquote> |
| 1395 |
Version 3.5.8 includes some important new performance optimizations |
| 1396 |
in the virtual machine code generator, including constant subexpression |
| 1397 |
factoring and common subexpression elimination. This release also |
| 1398 |
creates new public interfaces: |
| 1399 |
<a href="c3ref/randomness.html">sqlite3_randomness()</a> provides access to SQLite's internal |
| 1400 |
pseudo-random number generator, <a href="c3ref/limit.html">sqlite3_limit()</a> allows size |
| 1401 |
limits to be set at run-time on a per-connection basis, and |
| 1402 |
<a href="c3ref/context_db_handle.html">sqlite3_context_db_handle()</a> is a convenience routine that allows |
| 1403 |
an application-defined SQL function implementation to retrieve |
| 1404 |
its <a href="c3ref/sqlite3.html">database connection</a> handle.</p> |
| 1405 |
|
| 1406 |
<p> This release of SQLite is considered stable and ready for production use. |
| 1407 |
</blockquote><hr width="50%"><a name="2008_03_17"></a><h3>2008-03-17 - Version 3.5.7</h3><blockquote> |
| 1408 |
Version 3.5.7 fixes several minor and obscure bugs, especially |
| 1409 |
in the autoconf-generated makefile. Upgrading is optional. |
| 1410 |
This release of SQLite is considered stable and ready for production use. |
| 1411 |
</blockquote><hr width="50%"><a name="2008_02_06"></a><h3>2008-02-06 - Version 3.5.6</h3><blockquote> |
| 1412 |
Version 3.5.6 fixes a minor regression in 3.5.5 - a regression that |
| 1413 |
had nothing to do with the massive change of the virtual machine |
| 1414 |
to a register-based design. |
| 1415 |
No problems have been reported with the new virtual machine. This |
| 1416 |
release of SQLite is considered stable and ready for production use. |
| 1417 |
</blockquote><hr width="50%"><a name="2008_01_31"></a><h3>2008-01-31 - Version 3.5.5</h3><blockquote> |
| 1418 |
Version 3.5.5 changes over 8% of the core source code of SQLite in order |
| 1419 |
to convert the internal virtual machine from a stack-based design into |
| 1420 |
a register-based design. This change will allow future optimizations |
| 1421 |
and will avoid an entire class of stack overflow bugs that have caused |
| 1422 |
problems in the past. Even though this change is large, extensive testing |
| 1423 |
has found zero errors in the new virtual machine and so we believe this |
| 1424 |
to be a very stable release. |
| 1425 |
</blockquote><hr width="50%"><a name="2007_12_14"></a><h3>2007-12-14 - Version 3.5.4</h3><blockquote> |
| 1426 |
Version 3.5.4 fixes a long-standing but obscure bug in UPDATE and |
| 1427 |
DELETE which might cause database corruption. (See ticket #2832.) |
| 1428 |
Upgrading is recommended for all users.</p> |
| 1429 |
|
| 1430 |
<p> This release also brings the processing of ORDER BY statements into |
| 1431 |
compliance with standard SQL. This could, in theory, cause problems |
| 1432 |
for existing applications that depend on the older, buggy behavior. |
| 1433 |
See ticket #2822 for additional information. |
| 1434 |
</blockquote><hr width="50%"><a name="2007_12_12"></a><h3>2007-12-12 - SQLite Consortium Announced</h3><blockquote> |
| 1435 |
The <a href="consortium.html">SQLite Consortium</a> was launched |
| 1436 |
today with <a href="http://www.mozilla.org/">Mozilla</a> and |
| 1437 |
<a href="http://www.symbian.com/">Symbian</a> as charter members. |
| 1438 |
As noted in the <a href="pressrelease-20071212.html">press release</a>, |
| 1439 |
the Consortium's goal is to promote the continuing vitality and |
| 1440 |
independence of SQLite. |
| 1441 |
</blockquote><hr width="50%"><a name="2007_11_27"></a><h3>2007-11-27 - Version 3.5.3</h3><blockquote> |
| 1442 |
This is an incremental release that fixes several minor problems. |
| 1443 |
Upgrading is optional. If Version 3.5.2 or 3.5.1 is working fine |
| 1444 |
for you, then there is no pressing need to change to 3.5.3.</p> |
| 1445 |
|
| 1446 |
<p> The prebuilt binaries and the amalgamation found on the |
| 1447 |
<a href="download.html">download</a> page include the FTS3 fulltext |
| 1448 |
search extension module. We are doing this on an experimental |
| 1449 |
basis and are not promising to provide prebuilt binaries with |
| 1450 |
FTS3 in the future. |
| 1451 |
</blockquote><hr width="50%"><a name="2007_11_05"></a><h3>2007-11-05 - Version 3.5.2</h3><blockquote> |
| 1452 |
This is an incremental release that fixes several minor problems, |
| 1453 |
adds some obscure features, and provides some performance tweaks. |
| 1454 |
Upgrading is optional.</p> |
| 1455 |
|
| 1456 |
<p> The experimental compile-time option |
| 1457 |
<a href="compile.html#omitfeatures">SQLITE_OMIT_MEMORY_ALLOCATION</a> is no longer supported. On the other |
| 1458 |
hand, it is now possible to compile SQLite so that it uses a static |
| 1459 |
array for all its dynamic memory allocation needs and never calls |
| 1460 |
malloc. Expect to see additional radical changes to the memory |
| 1461 |
allocation subsystem in future releases. |
| 1462 |
</blockquote><hr width="50%"><a name="2007_10_04"></a><h3>2007-10-04 - Version 3.5.1</h3><blockquote> |
| 1463 |
Fix a long-standing bug that might cause database corruption if a |
| 1464 |
disk-full error occurs in the middle of a transaction and that |
| 1465 |
transaction is not rolled back. |
| 1466 |
Ticket #2686.</p> |
| 1467 |
|
| 1468 |
<p> The new VFS layer is stable. However, we still reserve the right to |
| 1469 |
make tweaks to the interface definition of the VFS if necessary. |
| 1470 |
</blockquote><hr width="50%"><a name="2007_09_04"></a><h3>2007-09-04 - Version 3.5.0 alpha</h3><blockquote> |
| 1471 |
The OS interface layer and the memory allocation subsystems in |
| 1472 |
SQLite have been reimplemented. The published API is largely unchanged |
| 1473 |
but the (unpublished) OS interface has been modified extensively. |
| 1474 |
Applications that implement their own OS interface will require |
| 1475 |
modification. See |
| 1476 |
<a href="34to35.html">34to35.html</a> for details.<p></p> |
| 1477 |
|
| 1478 |
<p> This is a large change. Approximately 10% of the source code was |
| 1479 |
modified. We are calling this first release "alpha" in order to give |
| 1480 |
the user community time to test and evaluate the changes before we |
| 1481 |
freeze the new design. |
| 1482 |
</blockquote><hr width="50%"><a name="2007_08_13"></a><h3>2007-08-13 - Version 3.4.2</h3><blockquote> |
| 1483 |
While stress-testing the |
| 1484 |
<a href="c3ref/soft_heap_limit.html">soft_heap_limit</a> |
| 1485 |
feature, a bug that could lead to |
| 1486 |
database corruption was discovered and fixed. |
| 1487 |
Though the consequences of this bug are severe, the chances of hitting |
| 1488 |
it in a typical application are remote. Upgrading is recommended |
| 1489 |
only if you use the |
| 1490 |
<a href="c3ref/soft_heap_limit.html">sqlite3_soft_heap_limit</a> |
| 1491 |
interface. |
| 1492 |
</blockquote><hr width="50%"><a name="2007_07_20"></a><h3>2007-07-20 - Version 3.4.1</h3><blockquote> |
| 1493 |
This release fixes a bug in <a href="lang_vacuum.html">VACUUM</a> that |
| 1494 |
can lead to database corruption. The bug was introduced in version |
| 1495 |
<a href="changes.html#version_3_3_14">3.3.14</a>. |
| 1496 |
Upgrading is recommended for all users. Also included are a slew of |
| 1497 |
other more routine |
| 1498 |
<a href="changes.html#version_3_4_1">enhancements and bug fixes</a>. |
| 1499 |
</blockquote><hr width="50%"><a name="2007_06_18"></a><h3>2007-06-18 - Version 3.4.0</h3><blockquote> |
| 1500 |
This release fixes two separate bugs either of which |
| 1501 |
can lead to database corruption. Upgrading |
| 1502 |
is strongly recommended. If you must continue using an older version |
| 1503 |
of SQLite, please at least read about how to avoid these bugs |
| 1504 |
at CorruptionFollowingBusyError and ticket #2418 |
| 1505 |
<p> |
| 1506 |
This release also adds explicit <a href="limits.html">limits</a> on the |
| 1507 |
sizes and quantities of things SQLite will handle. The new limits might |
| 1508 |
causes compatibility problems for existing applications that |
| 1509 |
use excessively large strings, BLOBs, tables, or SQL statements. |
| 1510 |
The new limits can be increased at compile-time to work around any problems |
| 1511 |
that arise. Nevertheless, the version number of this release is |
| 1512 |
3.4.0 instead of 3.3.18 in order to call attention to the possible |
| 1513 |
incompatibility. |
| 1514 |
</p> |
| 1515 |
There are also new features, including |
| 1516 |
<a href="c3ref/blob_open.html">incremental BLOB I/O</a> and |
| 1517 |
<a href="pragma.html#pragma_incremental_vacuum">incremental vacuum</a>. |
| 1518 |
See the <a href="changes.html#version_3_4_0">change log</a> |
| 1519 |
for additional information. |
| 1520 |
</blockquote><hr width="50%"><a name="2007_04_25"></a><h3>2007-04-25 - Version 3.3.17</h3><blockquote> |
| 1521 |
This version fixes a bug in the forwards-compatibility logic of SQLite |
| 1522 |
that was causing a database to become unreadable when it should have |
| 1523 |
been read-only. Upgrade from 3.3.16 only if you plan to deploy into |
| 1524 |
a product that might need to be upgraded in the future. For day to day |
| 1525 |
use, it probably does not matter. |
| 1526 |
</blockquote><hr width="50%"><a name="2007_04_18"></a><h3>2007-04-18 - Version 3.3.16</h3><blockquote> |
| 1527 |
Performance improvements added in 3.3.14 but mistakenly turned off |
| 1528 |
in 3.3.15 have been reinstated. A bug has been fixed that prevented |
| 1529 |
VACUUM from running if a NULL value was in a UNIQUE column. |
| 1530 |
</blockquote><hr width="50%"><a name="2007_04_09"></a><h3>2007-04-09 - Version 3.3.15</h3><blockquote> |
| 1531 |
An annoying bug introduced in 3.3.14 has been fixed. There are |
| 1532 |
also many enhancements to the test suite. |
| 1533 |
</blockquote><hr width="50%"><a name="2007_04_02"></a><h3>2007-04-02 - Version 3.3.14</h3><blockquote> |
| 1534 |
This version focuses on performance improvements. If you recompile |
| 1535 |
the amalgamation using GCC option -O3 (the precompiled binaries |
| 1536 |
use -O2) you may see performance |
| 1537 |
improvements of 35% or more over version 3.3.13 depending on your |
| 1538 |
workload. This version also |
| 1539 |
adds support for <a href="pragma.html#pragma_locking_mode"> |
| 1540 |
exclusive access mode</a>. |
| 1541 |
</blockquote><hr width="50%"><a name="2007_02_13"></a><h3>2007-02-13 - Version 3.3.13</h3><blockquote> |
| 1542 |
This version fixes a subtle bug in the ORDER BY optimizer that can |
| 1543 |
occur when using joins. There are also a few minor enhancements. |
| 1544 |
Upgrading is recommended. |
| 1545 |
</blockquote><hr width="50%"><a name="2007_01_27"></a><h3>2007-01-27 - Version 3.3.12</h3><blockquote> |
| 1546 |
The first published build of the previous version used the wrong |
| 1547 |
set of source files. Consequently, many people downloaded a build |
| 1548 |
that was labeled as "3.3.11" but was really 3.3.10. Version 3.3.12 |
| 1549 |
is released to clear up the ambiguity. A couple more bugs have |
| 1550 |
also been fixed and <a href="pragma.html#pragma_integrity_check"> |
| 1551 |
PRAGMA integrity_check</a> has been enhanced. |
| 1552 |
</blockquote><hr width="50%"><a name="2007_01_22"></a><h3>2007-01-22 - Version 3.3.11</h3><blockquote> |
| 1553 |
Version 3.3.11 fixes for a few more problems in version 3.3.9 that |
| 1554 |
version 3.3.10 failed to catch. Upgrading is recommended. |
| 1555 |
</blockquote><hr width="50%"><a name="2007_01_09"></a><h3>2007-01-09 - Version 3.3.10</h3><blockquote> |
| 1556 |
Version 3.3.10 fixes several bugs that were introduced by the previous |
| 1557 |
release. Upgrading is recommended. |
| 1558 |
</blockquote><hr width="50%"><a name="2007_01_04"></a><h3>2007-01-04 - Version 3.3.9</h3><blockquote> |
| 1559 |
Version 3.3.9 fixes bugs that can lead to database corruption under |
| 1560 |
obscure and difficult to reproduce circumstances. See |
| 1561 |
DatabaseCorruption in the |
| 1562 |
wiki for details. |
| 1563 |
This release also adds the new |
| 1564 |
<a href="c3ref/prepare.html">sqlite3_prepare_v2()</a> |
| 1565 |
API and includes important bug fixes in the command-line |
| 1566 |
shell and enhancements to the query optimizer. Upgrading is |
| 1567 |
recommended. |
| 1568 |
</blockquote><hr width="50%"><a name="2006_10_09"></a><h3>2006-10-09 - Version 3.3.8</h3><blockquote> |
| 1569 |
Version 3.3.8 adds support for full-text search using the |
| 1570 |
FTS1 module. There are also minor bug fixes. Upgrade only if |
| 1571 |
you want to try out the new full-text search capabilities or if |
| 1572 |
you are having problems with 3.3.7. |
| 1573 |
</blockquote><hr width="50%"><a name="2006_08_12"></a><h3>2006-08-12 - Version 3.3.7</h3><blockquote> |
| 1574 |
Version 3.3.7 includes support for loadable extensions and virtual |
| 1575 |
tables. But both features are still considered "beta" and their |
| 1576 |
APIs are subject to change in a future release. This release is |
| 1577 |
mostly to make available the minor bug fixes that have accumulated |
| 1578 |
since 3.3.6. Upgrading is not necessary. Do so only if you encounter |
| 1579 |
one of the obscure bugs that have been fixed or if you want to try |
| 1580 |
out the new features. |
| 1581 |
</blockquote><hr width="50%"><a name="2006_06_19"></a><h3>2006-06-19 - New Book About SQLite</h3><blockquote> |
| 1582 |
<i><a href="https://link.springer.com/book/10.1007/978-1-4302-3226-1">The Definitive Guide to SQLite</a></i>, |
| 1583 |
a 2nd edition book by Mike Owens and Grant Allen, |
| 1584 |
is now available from <a href="http://www.apress.com">Apress</a>. |
| 1585 |
The books covers the latest SQLite internals as well as |
| 1586 |
the native C interface and bindings for PHP, Python, |
| 1587 |
Perl, Ruby, Tcl, and Java. Recommended. |
| 1588 |
</blockquote><hr width="50%"><a name="2006_06_6"></a><h3>2006-06-6 - Version 3.3.6</h3><blockquote> |
| 1589 |
Changes include improved tolerance for Windows virus scanners |
| 1590 |
and faster :memory: databases. There are also fixes for several |
| 1591 |
obscure bugs. Upgrade if you are having problems. |
| 1592 |
</blockquote><hr width="50%"><a name="2006_04_5"></a><h3>2006-04-5 - Version 3.3.5</h3><blockquote> |
| 1593 |
This release fixes many minor bugs and documentation typos and |
| 1594 |
provides some minor new features and performance enhancements. |
| 1595 |
Upgrade only if you are having problems or need one of the new features. |
| 1596 |
</blockquote><hr width="50%"><a name="2006_02_11"></a><h3>2006-02-11 - Version 3.3.4</h3><blockquote> |
| 1597 |
This release fixes several bugs, including a |
| 1598 |
blunder that might cause a deadlock on multithreaded systems. |
| 1599 |
Anyone using SQLite in a multithreaded environment should probably upgrade. |
| 1600 |
</blockquote><hr width="50%"><a name="2006_01_31"></a><h3>2006-01-31 - Version 3.3.3 stable</h3><blockquote> |
| 1601 |
There have been no major problems discovered in version 3.3.2, so |
| 1602 |
we hereby declare the new APIs and language features to be stable |
| 1603 |
and supported. |
| 1604 |
</blockquote><hr width="50%"><a name="2006_01_24"></a><h3>2006-01-24 - Version 3.3.2 beta</h3><blockquote> |
| 1605 |
More bug fixes and performance improvements as we move closer to |
| 1606 |
a production-ready version 3.3.x. |
| 1607 |
</blockquote><hr width="50%"><a name="2006_01_16"></a><h3>2006-01-16 - Version 3.3.1 alpha</h3><blockquote> |
| 1608 |
Many bugs found in last week's alpha release have now been fixed and |
| 1609 |
the library is running much faster again.</p> |
| 1610 |
|
| 1611 |
<p> Database connections can now be moved between threads as long as the |
| 1612 |
connection holds no locks at the time it is moved. Thus the common |
| 1613 |
paradigm of maintaining a pool of database connections and handing |
| 1614 |
them off to transient worker threads is now supported. |
| 1615 |
Please help test this new feature. |
| 1616 |
See the MultiThreading wiki page for additional |
| 1617 |
information. |
| 1618 |
</blockquote><hr width="50%"><a name="2006_01_10"></a><h3>2006-01-10 - Version 3.3.0 alpha</h3><blockquote> |
| 1619 |
Version 3.3.0 adds support for CHECK constraints, DESC indices, |
| 1620 |
separate REAL and INTEGER column affinities, a new OS interface layer |
| 1621 |
design, and many other changes. The code passed a regression |
| 1622 |
test but should still be considered alpha. Please report any |
| 1623 |
problems.</p> |
| 1624 |
|
| 1625 |
<p> The file format for version 3.3.0 has changed slightly to support |
| 1626 |
descending indices and |
| 1627 |
a more efficient encoding of boolean values. SQLite 3.3.0 will read and |
| 1628 |
write legacy databases created with any prior version of SQLite 3. But |
| 1629 |
databases created by version 3.3.0 will not be readable or writable |
| 1630 |
by earlier versions of the SQLite. The older file format can be |
| 1631 |
specified at compile-time for those rare cases where it is needed. |
| 1632 |
</blockquote><hr width="50%"><a name="2005_12_19"></a><h3>2005-12-19 - Versions 3.2.8 and 2.8.17</h3><blockquote> |
| 1633 |
These versions contain one-line changes to 3.2.7 and 2.8.16 to fix a bug |
| 1634 |
that has been present since March of 2002 and version 2.4.0. |
| 1635 |
That bug might possibly cause database corruption if a large INSERT or |
| 1636 |
UPDATE statement within a multi-statement transaction fails due to a |
| 1637 |
uniqueness constraint but the containing transaction commits. |
| 1638 |
</blockquote><hr width="50%"><a name="2005_09_24"></a><h3>2005-09-24 - Version 3.2.7</h3><blockquote> |
| 1639 |
This version fixes several minor and obscure bugs. |
| 1640 |
Upgrade only if you are having problems. |
| 1641 |
</blockquote><hr width="50%"><a name="2005_09_16"></a><h3>2005-09-16 - Version 3.2.6 - Critical Bug Fix</h3><blockquote> |
| 1642 |
This version fixes a bug that can result in database |
| 1643 |
corruption if a VACUUM of a 1 gigabyte or larger database fails |
| 1644 |
(perhaps do to running out of disk space or an unexpected power loss) |
| 1645 |
and is later rolled back. |
| 1646 |
<p> |
| 1647 |
Also in this release: |
| 1648 |
The ORDER BY and GROUP BY processing was rewritten to use less memory. |
| 1649 |
Support for COUNT(DISTINCT) was added. The LIKE operator can now be |
| 1650 |
used by the optimizer on columns with COLLATE NOCASE. |
| 1651 |
</blockquote><hr width="50%"><a name="2005_08_27"></a><h3>2005-08-27 - Version 3.2.5</h3><blockquote> |
| 1652 |
This release fixes a few more lingering bugs in the new code. |
| 1653 |
We expect that this release will be stable and ready for production use. |
| 1654 |
</blockquote><hr width="50%"><a name="2005_08_24"></a><h3>2005-08-24 - Version 3.2.4</h3><blockquote> |
| 1655 |
This release fixes a bug in the new optimizer that can lead to segfaults |
| 1656 |
when parsing very complex WHERE clauses. |
| 1657 |
</blockquote><hr width="50%"><a name="2005_08_21"></a><h3>2005-08-21 - Version 3.2.3</h3><blockquote> |
| 1658 |
This release adds the <a href="lang_analyze.html">ANALYZE</a> command, |
| 1659 |
the <a href="lang_expr.html">CAST</a> operator, and many |
| 1660 |
very substantial improvements to the query optimizer. See the |
| 1661 |
<a href="changes.html#version_3_2_3">change log</a> for additional |
| 1662 |
information. |
| 1663 |
</blockquote><hr width="50%"><a name="2005_08_02"></a><h3>2005-08-02 - 2005 Open Source Award for SQLite</h3><blockquote> |
| 1664 |
SQLite and its primary author D. Richard Hipp have been honored with a |
| 1665 |
<a href="https://developers.google.com/open-source/osa#2005-google-oreilly-open-source-award-winners">2005 Open Source Award</a> |
| 1666 |
from Google and O'Reilly.<br clear="right"> |
| 1667 |
</blockquote><hr width="50%"><a name="2005_06_13"></a><h3>2005-06-13 - Version 3.2.2</h3><blockquote> |
| 1668 |
This release includes numerous minor bug fixes, speed improvements, |
| 1669 |
and code size reductions. There is no reason to upgrade unless you |
| 1670 |
are having problems or unless you just want to. |
| 1671 |
</blockquote><hr width="50%"><a name="2005_03_29"></a><h3>2005-03-29 - Version 3.2.1</h3><blockquote> |
| 1672 |
This release fixes a memory allocation problem in the new |
| 1673 |
<a href="lang_altertable.html">ALTER TABLE ADD COLUMN</a> |
| 1674 |
command. |
| 1675 |
</blockquote><hr width="50%"><a name="2005_03_21"></a><h3>2005-03-21 - Version 3.2.0</h3><blockquote> |
| 1676 |
The primary purpose for version 3.2.0 is to add support for |
| 1677 |
<a href="lang_altertable.html">ALTER TABLE ADD COLUMN</a>. |
| 1678 |
The new ADD COLUMN capability is made |
| 1679 |
possible by AOL developers supporting and embracing great |
| 1680 |
open-source software. Thanks, AOL!</p> |
| 1681 |
|
| 1682 |
<p> Version 3.2.0 also fixes an obscure but serious bug that was discovered |
| 1683 |
just prior to release. If you have a multi-statement transaction and |
| 1684 |
within that transaction an UPDATE or INSERT statement fails due to a |
| 1685 |
constraint, then you try to rollback the whole transaction, the rollback |
| 1686 |
might not work correctly. See |
| 1687 |
Ticket #1171 for details. Upgrading is recommended for all users. |
| 1688 |
</blockquote><hr width="50%"><a name="2005_03_16"></a><h3>2005-03-16 - Version 3.1.6</h3><blockquote> |
| 1689 |
Version 3.1.6 fixes a critical bug that can cause database corruption |
| 1690 |
when inserting rows into tables with around 125 columns. This bug was |
| 1691 |
introduced in version 3.0.0. See |
| 1692 |
Ticket #1163 for additional information. |
| 1693 |
</blockquote><hr width="50%"><a name="2005_03_11"></a><h3>2005-03-11 - Versions 3.1.4 and 3.1.5 Released</h3><blockquote> |
| 1694 |
Version 3.1.4 fixes a critical bug that could cause database corruption |
| 1695 |
if the autovacuum mode of version 3.1.0 is turned on (it is off by |
| 1696 |
default) and a CREATE UNIQUE INDEX is executed within a transaction but |
| 1697 |
fails because the indexed columns are not unique. Anyone using the |
| 1698 |
autovacuum feature and unique indices should upgrade.</p> |
| 1699 |
|
| 1700 |
<p> Version 3.1.5 adds the ability to disable |
| 1701 |
the F_FULLFSYNC ioctl() in OS-X by setting "PRAGMA synchronous=on" instead |
| 1702 |
of the default "PRAGMA synchronous=full". There was an attempt to add |
| 1703 |
this capability in 3.1.4 but it did not work due to a spelling error. |
| 1704 |
</blockquote><hr width="50%"><a name="2005_02_19"></a><h3>2005-02-19 - Version 3.1.3 Released</h3><blockquote> |
| 1705 |
Version 3.1.3 cleans up some minor issues discovered in version 3.1.2. |
| 1706 |
</blockquote><hr width="50%"><a name="2005_02_15"></a><h3>2005-02-15 - Versions 2.8.16 and 3.1.2 Released</h3><blockquote> |
| 1707 |
A critical bug in the VACUUM command that can lead to database |
| 1708 |
corruption has been fixed in both the 2.x branch and the main |
| 1709 |
3.x line. This bug has existed in all prior versions of SQLite. |
| 1710 |
Even though it is unlikely you will ever encounter this bug, |
| 1711 |
it is suggested that all users upgrade. See |
| 1712 |
ticket #1116 for additional information.</p> |
| 1713 |
|
| 1714 |
<p> Version 3.1.2 is also the first stable release of the 3.1 |
| 1715 |
series. SQLite 3.1 features added support for correlated |
| 1716 |
subqueries, autovacuum, autoincrement, ALTER TABLE, and |
| 1717 |
other enhancements. See the |
| 1718 |
<a href="releaselog/3_1_0.html">release notes |
| 1719 |
for version 3.1.0</a> for a detailed description of the |
| 1720 |
changes available in the 3.1 series. |
| 1721 |
</blockquote><hr width="50%"><a name="2005_02_01"></a><h3>2005-02-01 - Version 3.1.1 (beta) Released</h3><blockquote> |
| 1722 |
Version 3.1.1 (beta) is now available on the |
| 1723 |
website. Version 3.1.1 is fully backwards compatible with the 3.0 series |
| 1724 |
and features many new features including Autovacuum and correlated |
| 1725 |
subqueries. The |
| 1726 |
<a href="releaselog/3_1_1.html">release notes</a> |
| 1727 |
From version 3.1.0 apply equally to this release beta. A stable release |
| 1728 |
is expected within a couple of weeks. |
| 1729 |
</blockquote><hr width="50%"><a name="2005_01_21"></a><h3>2005-01-21 - Version 3.1.0 (alpha) Released</h3><blockquote> |
| 1730 |
Version 3.1.0 (alpha) is now available on the |
| 1731 |
website. Version 3.1.0 is fully backwards compatible with the 3.0 series |
| 1732 |
and features many new features including Autovacuum and correlated |
| 1733 |
subqueries. See the |
| 1734 |
<a href="releaselog/3_1_0.html">release notes</a> |
| 1735 |
for details.</p> |
| 1736 |
|
| 1737 |
<p> This is an alpha release. A beta release is expected in about a week |
| 1738 |
with the first stable release to follow after two more weeks. |
| 1739 |
</blockquote><hr width="50%"><a name="2004_11_09"></a><h3>2004-11-09 - SQLite at the 2004 International PHP Conference</h3><blockquote> |
| 1740 |
There was a talk on the architecture of SQLite and how to optimize |
| 1741 |
SQLite queries at the 2004 International PHP Conference in Frankfurt, |
| 1742 |
Germany.<br> |
| 1743 |
Obsolete URL: https://sqlite.org/php2004/page-001.html <br> |
| 1744 |
Slides from that talk are available. |
| 1745 |
</blockquote><hr width="50%"><a name="2004_10_11"></a><h3>2004-10-11 - Version 3.0.8</h3><blockquote> |
| 1746 |
Version 3.0.8 of SQLite contains several code optimizations and minor |
| 1747 |
bug fixes and adds support for DEFERRED, IMMEDIATE, and EXCLUSIVE |
| 1748 |
transactions. This is an incremental release. There is no reason |
| 1749 |
to upgrade from version 3.0.7 if that version is working for you. |
| 1750 |
</blockquote><hr width="50%"><a name="2004_10_10"></a><h3>2004-10-10 - SQLite at the 11<sup><small>th</small></sup> |
| 1751 |
Annual Tcl/Tk Conference</h3><blockquote> |
| 1752 |
There will be a talk on the use of SQLite in Tcl/Tk at the |
| 1753 |
11<sup><small>th</small></sup> Tcl/Tk Conference this week in |
| 1754 |
New Orleans. Visit <a href="http://www.tcl-lang.org/community/tcl2004/">http://www.tcl-lang.org/community/tcl2004/</a> |
| 1755 |
for details.<br> |
| 1756 |
Obsolete URL: https://sqlite.org/tclconf2004/page-001.html <br> |
| 1757 |
Slides from the talk are available. |
| 1758 |
</blockquote><hr width="50%"><a name="2004_09_18"></a><h3>2004-09-18 - Version 3.0.7</h3><blockquote> |
| 1759 |
Version 3.0 has now been in use by multiple projects for several |
| 1760 |
months with no major difficulties. We consider it stable and |
| 1761 |
ready for production use. |
| 1762 |
</blockquote><hr width="50%"><a name="2004_09_02"></a><h3>2004-09-02 - Version 3.0.6 (beta)</h3><blockquote> |
| 1763 |
Because of some important changes to sqlite3_step(), |
| 1764 |
we have decided to |
| 1765 |
do an additional beta release prior to the first "stable" release. |
| 1766 |
If no serious problems are discovered in this version, we will |
| 1767 |
release version 3.0 "stable" in about a week. |
| 1768 |
</blockquote><hr width="50%"><a name="2004_08_29"></a><h3>2004-08-29 - Version 3.0.5 (beta)</h3><blockquote> |
| 1769 |
The fourth beta release of SQLite version 3.0 is now available. |
| 1770 |
The next release is expected to be called "stable". |
| 1771 |
</blockquote><hr width="50%"><a name="2004_08_08"></a><h3>2004-08-08 - Version 3.0.4 (beta)</h3><blockquote> |
| 1772 |
The third beta release of SQLite version 3.0 is now available. |
| 1773 |
This new beta fixes several bugs including a database corruption |
| 1774 |
problem that can occur when doing a DELETE while a SELECT is pending. |
| 1775 |
Expect at least one more beta before version 3.0 goes final. |
| 1776 |
</blockquote><hr width="50%"><a name="2004_07_22"></a><h3>2004-07-22 - Version 3.0.3 (beta)</h3><blockquote> |
| 1777 |
The second beta release of SQLite version 3.0 is now available. |
| 1778 |
This new beta fixes many bugs and adds support for databases with |
| 1779 |
varying page sizes. The next 3.0 release will probably be called |
| 1780 |
a final or stable release.</p> |
| 1781 |
|
| 1782 |
<p> Version 3.0 adds support for internationalization and a new |
| 1783 |
more compact file format. |
| 1784 |
<a href="version3.html">Details.</a> |
| 1785 |
The API and file format have been fixed since 3.0.2. All |
| 1786 |
regression tests pass (over 100000 tests) and the test suite |
| 1787 |
exercises over 95% of the code.</p> |
| 1788 |
|
| 1789 |
<p> SQLite version 3.0 is made possible in part by AOL |
| 1790 |
developers supporting and embracing great Open-Source Software. |
| 1791 |
</blockquote><hr width="50%"><a name="2004_07_22"></a><h3>2004-07-22 - Version 2.8.15</h3><blockquote> |
| 1792 |
SQLite version 2.8.15 is a maintenance release for the version 2.8 |
| 1793 |
series. Version 2.8 continues to be maintained with bug fixes, but |
| 1794 |
no new features will be added to version 2.8. All the changes in |
| 1795 |
this release are minor. If you are not having problems, there is |
| 1796 |
there is no reason to upgrade. |
| 1797 |
</blockquote><hr width="50%"><a name="2004_06_30"></a><h3>2004-06-30 - Version 3.0.2 (beta) Released</h3><blockquote> |
| 1798 |
The first beta release of SQLite version 3.0 is now available. |
| 1799 |
Version 3.0 adds support for internationalization and a new |
| 1800 |
more compact file format. |
| 1801 |
<a href="version3.html">Details.</a> |
| 1802 |
As of this release, the API and file format are frozen. All |
| 1803 |
regression tests pass (over 100000 tests) and the test suite |
| 1804 |
exercises over 95% of the code.</p> |
| 1805 |
|
| 1806 |
<p> SQLite version 3.0 is made possible in part by AOL |
| 1807 |
developers supporting and embracing great Open-Source Software. |
| 1808 |
</blockquote><hr width="50%"><a name="2004_06_25"></a><h3>2004-06-25 - Website hacked</h3><blockquote> |
| 1809 |
The www.sqlite.org website was hacked sometime around 2004-06-22 |
| 1810 |
because the lead SQLite developer failed to properly patch CVS. |
| 1811 |
Evidence suggests that the attacker was unable to elevate privileges |
| 1812 |
above user "cvs". Nevertheless, as a precaution the entire website |
| 1813 |
has been reconstructed from scratch on a fresh machine. All services |
| 1814 |
should be back to normal as of 2004-06-28. |
| 1815 |
</blockquote><hr width="50%"><a name="2004_06_18"></a><h3>2004-06-18 - Version 3.0.0 (alpha) Released</h3><blockquote> |
| 1816 |
The first alpha release of SQLite version 3.0 is available for |
| 1817 |
public review and comment. Version 3.0 enhances internationalization support |
| 1818 |
through the use of UTF-16 and user-defined text collating sequences. |
| 1819 |
BLOBs can now be stored directly, without encoding. |
| 1820 |
A new file format results in databases that are 25% smaller (depending |
| 1821 |
on content). The code is also a little faster. In spite of the many |
| 1822 |
new features, the library footprint is still less than 240KB |
| 1823 |
(x86, gcc -O1). |
| 1824 |
<a href="version3.html">Additional information</a>.</p> |
| 1825 |
|
| 1826 |
<p> Our intent is to freeze the file format and API on 2004-07-01. |
| 1827 |
Users are encouraged to review and evaluate this alpha release carefully |
| 1828 |
and submit any feedback prior to that date.</p> |
| 1829 |
|
| 1830 |
<p> The 2.8 series of SQLite will continue to be supported with bug |
| 1831 |
fixes for the foreseeable future. |
| 1832 |
</blockquote><hr width="50%"><a name="2004_06_09"></a><h3>2004-06-09 - Version 2.8.14 Released</h3><blockquote> |
| 1833 |
SQLite version 2.8.14 is a patch release to the stable 2.8 series. |
| 1834 |
There is no reason to upgrade if 2.8.13 is working ok for you. |
| 1835 |
This is only a bug-fix release. Most development effort is |
| 1836 |
going into version 3.0.0 which is due out soon. |
| 1837 |
</blockquote><hr width="50%"><a name="2004_05_31"></a><h3>2004-05-31 - CVS Access Temporarily Disabled</h3><blockquote> |
| 1838 |
Anonymous access to the CVS repository will be suspended |
| 1839 |
for 2 weeks beginning on 2004-06-04. Everyone will still |
| 1840 |
be able to download |
| 1841 |
prepackaged source bundles, create or modify trouble tickets, or view |
| 1842 |
change logs during the CVS service interruption. Full open access to the |
| 1843 |
CVS repository will be restored on 2004-06-18. |
| 1844 |
</blockquote><hr width="50%"><a name="2004_04_23"></a><h3>2004-04-23 - Work Begins On SQLite Version 3</h3><blockquote> |
| 1845 |
Work has begun on version 3 of SQLite. Version 3 is a major |
| 1846 |
changes to both the C-language API and the underlying file format |
| 1847 |
that will enable SQLite to better support internationalization. |
| 1848 |
The first beta is schedule for release on 2004-07-01.</p> |
| 1849 |
|
| 1850 |
<p> Plans are to continue to support SQLite version 2.8 with |
| 1851 |
bug fixes. But all new development will occur in version 3.0. |
| 1852 |
</blockquote><hr width="50%"> |
| 1853 |
<p align="center"><small><i>This page was last updated on 2026-02-28 22:51:09Z </small></i></p> |
| 1854 |
|