-C Fix\sthe\smalloc-10\stest\sin\smalloc.test\sso\sthat\sit\swill\srun\son\swindows\swhen\ninvoked\sfrom\sexclusive3.test.\s(CVS\s4389)
-D 2007-09-04T01:25:49
+C More\sdocumentation\schanges\sprior\sto\sthe\s3.5.0\salpha\srelease.\s(CVS\s4390)
+D 2007-09-04T01:58:27
F Makefile.in cbfb898945536a8f9ea8b897e1586dd1fdbcc5db
F Makefile.linux-gcc 65241babba6faf1152bf86574477baab19190499
F README 9c4e2d6706bdcc3efdd773ce752a8cdab4f90028
F www/c_interface.tcl b51b08591554c16a0c3ef718364a508ac25abc7e
F www/capi3.tcl 88884dd743039d1a95aa57f4a5eb369de7744716
F www/capi3ref.tcl 167c2d5b45da22d77b2493b00d44b001b4ec83b1
-F www/changes.tcl 480f301f7945cc0348a0cc92905d37fe499eacd2
+F www/changes.tcl 679465d9e1d2f371bb93d99c3da76ac33751ba1e
F www/common.tcl 2b793e5c31486c8a01dd27dc0a631ad93704438e
F www/compile.tcl 276546d7eb445add5a867193bbd80f6919a6b084
F www/conflict.tcl cdd0f4b59b0ba6d61f67e6a38f3ae45853bacb30
F www/docs.tcl 09eeac4e565789a67abc63f166a9ae7f3050454d
F www/download.tcl d59a0244f22a975c3f9deafb535fc20549cb8c45
F www/dynload.tcl 02eb8273aa78cfa9070dd4501dca937fb22b466c
-F www/faq.tcl 745e87b2afc4deaf062aaee8649d50294de3f244
+F www/faq.tcl ebdcad6041d66220b866ac49bcd55726c3bd80ef
F www/fileformat.tcl 900c95b9633abc3dcfc384d9ddd8eb4876793059
F www/formatchng.tcl 722a9c08be4f7325b3a545abfe508cfbabe20eb7
F www/fullscanb.gif f7c94cb227f060511f8909e10f570157263e9a25
F www/index-ex1-x-b.gif f9b1d85c3fa2435cf38b15970c7e3aa1edae23a3
-F www/index.tcl 118db0f8ff6e1c6d90a8346e5e9a8b991c73516d
+F www/index.tcl 60a827e967bc1f36fd62fd23829009a93b8ad6a1
F www/indirect1b1.gif adfca361d2df59e34f9c5cac52a670c2bfc303a1
F www/lang.tcl bb73892bf99c81658ec46d0c7a87e54cd21d435b
F www/limits.tcl 9035eb73e814ccb298595fd57670dec817533616
F www/mingw.tcl d96b451568c5d28545fefe0c80bee3431c73f69c
F www/mkapidoc.tcl 2fdbb765c38a4467687ba390e07c1229d4939a3b
F www/nulls.tcl ec35193f92485b87b90a994a01d0171b58823fcf
-F www/oldnews.tcl 7d01490a7f2686baf3446647600a79c7a5855695
+F www/oldnews.tcl 11eb63e47e0bed91cd0d25984a38e44abf90c6a2
F www/omitted.tcl ee6b46f83d513b2187869740da829a700e1a355e
F www/opcode.tcl 5bd68059416b223515a680d410a9f7cb6736485f
F www/optimizer.tcl d6812a10269bd0d7c488987aac0ad5036cace9dc
F www/vdbe.tcl 87a31ace769f20d3627a64fa1fade7fed47b90d0
F www/version3.tcl 890248cf7b70e60c383b0e84d77d5132b3ead42b
F www/whentouse.tcl fc46eae081251c3c181bd79c5faef8195d7991a5
-P dced71a010c14a53e0f71841b5fd55108b7f88b3
-R fe4f8dbf329d720618e95c841905d656
+P 1166f9c7d1b3cb39a2ab96ed08a0552ba5fe1851
+R 839275865cf76c51de7d7f2af36036b8
U drh
-Z 69eacf5f608708f12a5b7d1ca5788549
+Z 72c2c5a8119d9f37d8e7f49a0d2759cc
-1166f9c7d1b3cb39a2ab96ed08a0552ba5fe1851
\ No newline at end of file
+b15b03dfd6baef696c80ba1621cd36b1dbec1286
\ No newline at end of file
}
-chng {2007 Sep 3 (3.5.0 beta)} {
+chng {2007 Sep 04 (3.5.0) alpha} {
<li>Redesign the OS interface layer. See
<a href="34to35.html">34to35.html</a> for details.
<font color="red">*** Potentially incompatible change ***</font>
#
# Run this script to generated a faq.html output file
#
-set rcsid {$Id: faq.tcl,v 1.39 2007/08/03 08:18:45 danielk1977 Exp $}
+set rcsid {$Id: faq.tcl,v 1.40 2007/09/04 01:58:27 drh Exp $}
source common.tcl
header {SQLite Frequently Asked Questions</title>}
Is SQLite threadsafe?
} {
<p>Yes. Sometimes. In order to be thread-safe, SQLite must be compiled
- with the THREADSAFE preprocessor macro set to 1. In the default
- distribution, the windows binaries are compiled to be threadsafe but
- the linux binaries are not. If you want to change this, you'll have to
- recompile.</p>
-
- <p>"Threadsafe" in the previous paragraph means that two or more threads
- can run SQLite at the same time on different "<b>sqlite3</b>" structures
- returned from separate calls to
- <a href="capi3ref.html#sqlite3_open">sqlite3_open()</a>. It is never safe
- to use the same <b>sqlite3</b> structure pointer in two
- or more threads.</p>
+ with the SQLITE_THREADSAFE preprocessor macro set to 1. Both the windows
+ and linux precompiled binaries in the distribution are compiled this way.
+ If you are unsure if the SQLite library you are linking against is compiled
+ to be threadsafe you can call the
+ <a href="capi3ref.html#sqlite3_threadsafe">sqlite3_threadsafe()</a>
+ interface to find out.
+ </p>
<p>Prior to version 3.3.1,
an <b>sqlite3</b> structure could only be used in the same thread
can safely assume that no locks are being held if no
transaction is pending and all statements have been finalized.</p>
- <p>If you turn on
- <a href="capi3ref.html#sqlite3_enable_shared_cache">shared cache</a>
- mode or if you compile with the -DSQLITE_ENABLE_MEMORY_MANAGEMENT=1
- option, then you can never move an <b>sqlite3</b> pointer across
- threads. The <b>sqlite3</b> pointer must only be used in the same
- thread in which it was created by
- <a href="capi3ref.html#sqlite3_open">sqlite3_open()</a>. If you
- break the rules and use an <b>sqlite3</b> handle in more than one
- thread under these circumstances you will likely corrupt some
- internal data structures, resulting in a crash.</p>
-
<p>Under UNIX, you should not carry an open SQLite database across
a fork() system call into the child process. Problems will result
if you do.</p>
puts "<hr width=\"50%\">"
}
-newsitem {2007-Sep-3} {Version 3.5.0 beta} {
+newsitem {2007-Sep-04} {Version 3.5.0 alpha} {
The OS interface layer and the memory allocation subsystems in
SQLite have been reimplemented. The published API is largely unchanged
but the (unpublished) OS interface has been modified extensively.
<a href="34to35.html">34to35.html</a> for details.<p>
This is a large change approximately 1 line of count of out 10 was
- modified. We are calling this first release "beta" in order to give
+ modified. We are calling this first release "alpha" in order to give
the user community time to test and evaluate the changes before we
freeze the new design.
}
<a href="changes.html#version_3_4_1">enhancements and bug fixes</a>.
}
-newsitem {2007-Jun-18} {Version 3.4.0} {
- This release fixes two separate bugs either of which
- can lead to database corruption. Upgrading
- is strongly recommended. If you must continue using an older version
- of SQLite, please at least read about how to avoid these bugs
- at
- <a href="http://www.sqlite.org/cvstrac/wiki?p=CorruptionFollowingBusyError">
- CorruptionFollowingBusyError</a> and
- <a href="http://www.sqlite.org/cvstrac/tktview?tn=2418">ticket #2418</a>
- <p>
- This release also adds explicit <a href="limits.html">limits</a> on the
- sizes and quantities of things SQLite will handle. The new limits might
- causes compatibility problems for existing applications that
- use excessively large strings, BLOBs, tables, or SQL statements.
- The new limits can be increased at compile-time to work around any problems
- that arise. Nevertheless, the version number of this release is
- 3.4.0 instead of 3.3.18 in order to call attention to the possible
- incompatibility.
- </p>
- There are also new features, including
- <a href="capi3ref.html#sqlite3_blob_open">incremental BLOB I/O</a> and
- <a href="pragma.html#pragma_incremental_vacuum">incremental vacuum</a>.
- See the <a href="changes.html#version_3_4_0">change log</a>
- for additional information.
-}
-
puts {
<p align="right"><a href="oldnews.html">Old news...</a></p>
</td></tr></table>
}
-footer {$Id: index.tcl,v 1.160 2007/09/03 20:32:46 drh Exp $}
+footer {$Id: index.tcl,v 1.161 2007/09/04 01:58:27 drh Exp $}
puts "<hr width=\"50%\">"
}
+newsitem {2007-Jun-18} {Version 3.4.0} {
+ This release fixes two separate bugs either of which
+ can lead to database corruption. Upgrading
+ is strongly recommended. If you must continue using an older version
+ of SQLite, please at least read about how to avoid these bugs
+ at
+ <a href="http://www.sqlite.org/cvstrac/wiki?p=CorruptionFollowingBusyError">
+ CorruptionFollowingBusyError</a> and
+ <a href="http://www.sqlite.org/cvstrac/tktview?tn=2418">ticket #2418</a>
+ <p>
+ This release also adds explicit <a href="limits.html">limits</a> on the
+ sizes and quantities of things SQLite will handle. The new limits might
+ causes compatibility problems for existing applications that
+ use excessively large strings, BLOBs, tables, or SQL statements.
+ The new limits can be increased at compile-time to work around any problems
+ that arise. Nevertheless, the version number of this release is
+ 3.4.0 instead of 3.3.18 in order to call attention to the possible
+ incompatibility.
+ </p>
+ There are also new features, including
+ <a href="capi3ref.html#sqlite3_blob_open">incremental BLOB I/O</a> and
+ <a href="pragma.html#pragma_incremental_vacuum">incremental vacuum</a>.
+ See the <a href="changes.html#version_3_4_0">change log</a>
+ for additional information.
+}
newsitem {2007-Apr-25} {Version 3.3.17} {
This version fixes a bug in the forwards-compatibility logic of SQLite
Plans are to continue to support SQLite version 2.8 with
bug fixes. But all new development will occur in version 3.0.
}
-footer {$Id: oldnews.tcl,v 1.22 2007/08/13 16:15:29 drh Exp $}
+footer {$Id: oldnews.tcl,v 1.23 2007/09/04 01:58:27 drh Exp $}