Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Update the version number and change comments in preparation for the release of 3.3.14. (CVS 3789) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
d9f6fdb72b29354921e6de40df5ed4f8 |
User & Date: | drh 2007-04-02 00:53:19.000 |
Context
2007-04-02
| ||
05:07 | Fix a resource leak introduced by the change-counter optimisation. Also add some test coverage. (CVS 3790) (check-in: ba0538a497 user: danielk1977 tags: trunk) | |
00:53 | Update the version number and change comments in preparation for the release of 3.3.14. (CVS 3789) (check-in: d9f6fdb72b user: drh tags: trunk) | |
2007-04-01
| ||
23:49 | Fix some warnings about unused and uninitialized variables. (CVS 3788) (check-in: 18aec1ddfb user: drh tags: trunk) | |
Changes
Changes to VERSION.
|
| | | 1 | 3.3.14 |
Changes to www/changes.tcl.
︙ | ︙ | |||
20 21 22 23 24 25 26 27 28 29 30 31 32 33 | if {[regexp {\(([0-9.]+)\)} $date all vers]} { set label [string map {. _} $vers] puts "<A NAME=\"version_$label\">" } puts "<DT><B>$date</B></DT>" puts "<DD><P><UL>$desc</UL></P></DD>" } 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 used by an expression. This feature is considered experimental pending additional testing.</li> <li>Allow up to 64 tables in a join - the old limit was 32.</li> | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 | if {[regexp {\(([0-9.]+)\)} $date all vers]} { set label [string map {. _} $vers] puts "<A NAME=\"version_$label\">" } puts "<DT><B>$date</B></DT>" 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 used by an expression. This feature is considered experimental pending additional testing.</li> <li>Allow up to 64 tables in a join - the old limit was 32.</li> |
︙ | ︙ |
Changes to www/pragma.tcl.
1 2 3 | # # Run this Tcl script to generate the pragma.html file. # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # Run this Tcl script to generate the pragma.html file. # 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} proc Section {name {label {}}} { puts "\n<hr />" if {$label!=""} { puts "<a name=\"$label\"></a>" |
︙ | ︙ | |||
243 244 245 246 247 248 249 | <p>In NORMAL locking-mode (the default), a database connection unlocks the database file at the conclusion of each read or write transaction. When the locking-mode is set to EXCLUSIVE, the 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 | | | | | > > > > > > > > > > > > > > > > > > | 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 | <p>In NORMAL locking-mode (the default), a database connection unlocks the database file at the conclusion of each read or write transaction. When the locking-mode is set to EXCLUSIVE, the 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.</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 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.</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> <li><p><b>PRAGMA page_size; <br>PRAGMA page_size = </b><i>bytes</i><b>;</b></p> <p>Query or set the page-size of the database. The page-size may only be set if the database has not yet been created. The page |
︙ | ︙ |