Prepare for the release of version 3.3.0. (CVS 2913)

FossilOrigin-Name: 302993ae16750c56fd1418531ba716cff53d2df0

www/changes.tcl

@@ -25,18 +25,22 @@ proc chng {date desc} {
   puts "<DD><P><UL>$desc</UL></P></DD>"
 }
 
-chng {2006 January ? (3.3.0)} {
+chng {2006 January 10 (3.3.0 alpha)} {
 <li>CHECK constraints</li>
 <li>IF EXISTS and IF NOT EXISTS clauses on CREATE/DROP TABLE/INDEX.</li>
 <li>DESC indices</li>
 <li>More efficient encoding of boolean values resulting in smaller database
 files</li>
-<li>More aggressive SQLITE_OMIT_FLOATING_POINT<li>
+<li>More aggressive SQLITE_OMIT_FLOATING_POINT</li>
 <li>Separate INTEGER and REAL affinity</li>
-<li>Add a virtual function layer for the OS interface</li>
+<li>Added a virtual function layer for the OS interface</li>
 <li>"exists" method added to the TCL interface</li>
 <li>Improved response to out-of-memory errors</li>
-<li>Database cached shared between connections in the same thread</li>
+<li>Database cache can be optionally shared between connections
+in the same thread</li>
+<li>Optional READ UNCOMMITTED isolation (instead of the default
+isolation level of SERIALIZABLE) and table level locking when
+database connections share a common cache.</li>
 }
 
 chng {2005 December 19 (3.2.8)} {

www/faq.tcl

@@ -1,7 +1,7 @@
 #
 # Run this script to generated a faq.html output file
 #
-set rcsid {$Id: faq.tcl,v 1.32 2006/01/10 23:00:42 drh Exp $}
+set rcsid {$Id: faq.tcl,v 1.33 2006/01/11 01:08:34 drh Exp $}
 source common.tcl
 header {SQLite Frequently Asked Questions</title>}
 
@@ -202,9 +202,15 @@ faq {
   You cannot open a
   database in one thread then pass the handle off to another thread for
   it to use.  This is due to limitations (bugs?) in many common threading
-  implementations such as on RedHat9.  There may be ways to work around
-  these limitations, but they are complex and exceedingly difficult to
-  test for correctness.  For that reason, SQLite currently takes the safe
+  implementations such as on RedHat9.  Specifically, an fcntl() lock
+  created by one thread cannot be removed or modified by a different
+  thread on the troublesome systems.  And since SQLite uses fcntl()
+  locks heavily for concurrency control, serious problems arise if you 
+  start moving database connections across threads.</p>
+
+  <p>There may be ways to work around the fcntl() lock problems in Linux,
+  but they are complex and exceedingly difficult to test for correctness.
+  For that reason, SQLite currently takes the safe
   approach and disallows the sharing of handles among threads.</p>
 
   <p>Under UNIX, you should not carry an open SQLite database across

www/formatchng.tcl

@@ -1,7 +1,7 @@
 #
 # Run this Tcl script to generate the formatchng.html file.
 #
-set rcsid {$Id: formatchng.tcl,v 1.14 2005/03/23 01:05:14 drh Exp $ }
+set rcsid {$Id: formatchng.tcl,v 1.15 2006/01/11 01:08:34 drh Exp $ }
 source common.tcl
 header {File Format Changes in SQLite}
 puts {
@@ -211,6 +211,16 @@ occurred since version 1.0.0:
   SQLite versions.</p>
   </td>
 </tr>
+<tr>
+  <td valign="top">3.2.8 to 3.3.0</td>
+  <td valign="top">2006-Jan-10</td>
+  <td><p>Version 3.3.0 uses a new encoding for binary values that
+  uses less disk space.  Version 3.3.0 can read and write database
+  files created by prior versions of SQLite.  But prior versions
+  of SQLite will not be able to read or write databases created
+  by Version 3.3.0</p>
+  </td>
+</tr>
 </table>
 </blockquote>
 

www/index.tcl

@@ -66,6 +66,21 @@ proc newsitem {date title text} {
   puts "<hr width=\"50%\">"
 }
 
+newsitem {2006-Jan-10} {Version 3.3.0 alpha} {
+  Version 3.3.0 adds support for CHECK constraints, DESC indices,
+  separate REAL and INTEGER column affinities, a new OS interface layer
+  design, and many other changes.  The code passed a regression
+  test but should still be considered alpha.  Please report any
+  problems.
+
+  The file format for version 3.3.0 has changed slightly in order provide
+  a more efficient encoding of binary values.  SQLite 3.3.0 will read and
+  write legacy databases created with any prior version of SQLite 3.  But
+  databases created by version 3.3.0 will not be readable or writable
+  by earlier versions of the SQLite.  The older file format can be
+  specified at compile-time for those rare cases where it is needed.
+}
+
 newsitem {2005-Dec-19} {Versions 3.2.8 and 2.8.17} {
   These versions contain one-line changes to 3.2.7 and 2.8.16 to fix a bug
   that has been present since March of 2002 and version 2.4.0.
@@ -120,4 +135,4 @@ puts {
 <p align="right"><a href="oldnews.html">Old news...</a></p>
 </td></tr></table>
 }
-footer {$Id: index.tcl,v 1.128 2005/12/19 17:53:36 drh Exp $}
+footer {$Id: index.tcl,v 1.129 2006/01/11 01:08:34 drh Exp $}