Update the version number and change comments in preparation for the

release of 3.3.14. (CVS 3789)

FossilOrigin-Name: d9f6fdb72b29354921e6de40df5ed4f86b158a01
This commit is contained in:
drh 2007-04-02 00:53:18 +00:00
parent 61fc595fdd
commit 3057aaaa9c
5 changed files with 75 additions and 15 deletions

View File

@ -1 +1 @@
3.3.13
3.3.14

View File

@ -1,9 +1,9 @@
C Fix\ssome\swarnings\sabout\sunused\sand\suninitialized\svariables.\s(CVS\s3788)
D 2007-04-01T23:49:52
C Update\sthe\sversion\snumber\sand\schange\scomments\sin\spreparation\sfor\sthe\nrelease\sof\s3.3.14.\s(CVS\s3789)
D 2007-04-02T00:53:19
F Makefile.in 2f2c3bf69faf0ae7b8e8af4f94f1986849034530
F Makefile.linux-gcc 2d8574d1ba75f129aba2019f0b959db380a90935
F README 9c4e2d6706bdcc3efdd773ce752a8cdab4f90028
F VERSION e31cc83750f9f93f8c53236f6618cb876fdd9d1a
F VERSION ebbd5a08dc4d7f984b7e0f2dd3d5d78001119117
F aclocal.m4 d20ba55930a05197b484809fba1d2b603f4e67a6
F addopcodes.awk 701697fae48376375ec8532c3d04e910cfeef352
F art/2005osaward.gif 0d1851b2a7c1c9d0ccce545f3e14bca42d7fd248
@ -404,7 +404,7 @@ F www/autoinc.tcl b357f5ba954b046ee35392ce0f884a2fcfcdea06
F www/c_interface.tcl b51b08591554c16a0c3ef718364a508ac25abc7e
F www/capi3.tcl 7a7cc225fe02eb7ab861a6019b08baa0014409e1
F www/capi3ref.tcl 24fc13e145bdc07a77051d944534a97a957267ab
F www/changes.tcl dba0e1f40192f79c7a887fa3efa56e6fdd54f85a
F www/changes.tcl 7f1a3f6fbb7cc2bd0bf49af0bcbb02a316700a79
F www/common.tcl 2b793e5c31486c8a01dd27dc0a631ad93704438e
F www/compile.tcl 276546d7eb445add5a867193bbd80f6919a6b084
F www/conflict.tcl cdd0f4b59b0ba6d61f67e6a38f3ae45853bacb30
@ -435,7 +435,7 @@ F www/opcode.tcl 5bd68059416b223515a680d410a9f7cb6736485f
F www/optimizer.tcl d6812a10269bd0d7c488987aac0ad5036cace9dc
F www/optimizing.tcl f0b2538988d1bbad16cbfe63ec6e8f48c9eb04e5
F www/optoverview.tcl 815df406a38c9f69b27d37e8f7ede004c6d9f19e
F www/pragma.tcl 45dc06f5b92834bc835b394ae186719fe921d6e8
F www/pragma.tcl efbd34cedda8235e236840e1a2bc09e1d4ac39c5
F www/quickstart.tcl 8708a4ca83fbf55c66af1782992626f20c3df095
F www/shared.gif 265bae80c5b311c5a86e47662821076ffaf5c6ea
F www/sharedcache.tcl 3ebec81110e606af6fd65a3c4c19562cb173b29c
@ -447,7 +447,7 @@ F www/tclsqlite.tcl bb0d1357328a42b1993d78573e587c6dcbc964b9
F www/vdbe.tcl 87a31ace769f20d3627a64fa1fade7fed47b90d0
F www/version3.tcl 890248cf7b70e60c383b0e84d77d5132b3ead42b
F www/whentouse.tcl 97e2b5cd296f7d8057e11f44427dea8a4c2db513
P ddfc3b2df0b37be66fc55bb216cdcb6ba67aa7fd
R 6aaccc938ac434f31b7ba1499b082549
P 18aec1ddfb08b74f0ef9cf1215eac7af71449db3
R 1ba2c076c76000f21aa292bb0a8f72c4
U drh
Z 1690edfe26c670d8db633c5c98f82e61
Z ab035ae84bd6530ffbee25f61451be81

View File

@ -1 +1 @@
18aec1ddfb08b74f0ef9cf1215eac7af71449db3
d9f6fdb72b29354921e6de40df5ed4f86b158a01

View File

@ -25,6 +25,48 @@ proc chng {date desc} {
puts "<DD><P><UL>$desc</UL></P></DD>"
}
chng {2007 April 2 (3.3.14)} {
<li>Fix a <a href="http://www.sqlite.org/cvstrac/tktview?tn=2273">bug</a>
in 3.3.13 that could cause a segfault when the IN operator
is used one one term of a two-column index and the right-hand side of
the IN operator contains a NULL.</li>
<li>Added a new OS interface method for determining the sector size
of underlying media: sqlite3OsSectorSize().</li>
<li>A new algorithm for statements of the form
INSERT INTO <i>table1</i> SELECT * FROM <i>table2</i>
is faster and reduces fragmentation. VACUUM uses statements of
this form and thus runs faster and defragments better.</li>
<li>Performance enhancements through reductions in disk I/O:
<ul>
<li>Do not read the last page of an overflow chain when
deleting the row - just add that page to the freelist.</li>
<li>Do not store pages being deleted in the
rollback journal.</li>
<li>Do not read in the (meaningless) content of
pages extracted from the freelist.</li>
<li>Do not flush the page cache (and thus avoiding
a cache refill) unless another process changes the underlying
database file.</li>
<li>Truncate rather than delete the rollback journal when committing
a transaction in exclusive access mode, or when committing the TEMP
database.</li>
</ul></li>
<li>Added support for exclusive access mode using
<a href="pragma.html#pragma_locking_mode">
"PRAGMA locking_mode=EXCLUSIVE"</a></li>
<li>Use heap space instead of stack space for large buffers in the
pager - useful on embedded platforms with stack-space
limitations.</li>
<li>Add a makefile target "sqlite3.c" that builds an amalgamation containing
the core SQLite library C code in a single file.</li>
<li>Get the library working correctly when compiled
with GCC option "-fstrict-aliasing".</li>
<li>Removed the vestigal SQLITE_PROTOCOL error.</li>
<li>Improvements to test coverage, other minor bugs fixed,
memory leaks plugged,
code refactored and/or recommented in places for easier reading.</li>
}
chng {2007 February 13 (3.3.13)} {
<li>Add a "fragmentation" measurement in the output of sqlite3_analyzer.</li>
<li>Add the COLLATE operator used to explicitly set the collating sequence

View File

@ -1,7 +1,7 @@
#
# Run this Tcl script to generate the pragma.html file.
#
set rcsid {$Id: pragma.tcl,v 1.21 2007/03/26 08:41:13 danielk1977 Exp $}
set rcsid {$Id: pragma.tcl,v 1.22 2007/04/02 00:53:19 drh Exp $}
source common.tcl
header {Pragma statements supported by SQLite}
@ -247,20 +247,38 @@ puts {
database connection never releases file-locks. The first time the
database is read in EXCLUSIVE mode, a shared lock is obtained and
held. The first time the database is written, an exclusive lock is
obtained and held.
obtained and held.</p>
<p>Database locks obtained by a connection in EXCLUSIVE mode may be
released either by closing the database connection, or by setting the
locking-mode back to NORMAL using this pragma and then accessing the
database file (for read or write). Simply setting the locking-mode to
NORMAL is not enough, locks not be released until the next time
the database file is accessed.
NORMAL is not enough - locks are not be released until the next time
the database file is accessed.</p>
<p>There are two reasons to set the locking-mode to EXCLUSIVE. One
is if the application actually wants to prevent other processes from
accessing the database file. The other is that a small number of
filesystem operations are saved by optimizations enabled in this
mode. This may be significant in embedded environments.
mode. This may be significant in embedded environments.</p>
<p>When the locking_mode pragma specifies a particular database,
for example:</p>
<blockquote>
PRAGMA <b>main.</b>locking_mode=EXCLUSIVE;
</blockquote>
<p>Then the locking mode applies only to the named database. If no
database name qualifier preceeds the "locking_mode" keyword then
the locking mode is applied to all databases, including any new
databases added by subsequent <a href="lang_attach.html">ATTACH</a>
commands.</p>
<p>The "temp" database (in which TEMP tables and indices are stored)
always uses exclusive locking mode. The locking mode of temp cannot
be changed. All other databases use the normal locking mode by default
and are effected by this pragma.</p>
</li>
<a name="pragma_page_size"></a>