Prepare for the 3.3.1 alpha release. (CVS 2951)

FossilOrigin-Name: 3e32bcf0b8ee8d7a3f26ced8d5887561eeb3e7ab

www/capi3ref.tcl

@@ -1,4 +1,4 @@
-set rcsid {$Id: capi3ref.tcl,v 1.28 2006/01/11 23:40:34 drh Exp $}
+set rcsid {$Id: capi3ref.tcl,v 1.29 2006/01/15 18:29:18 drh Exp $}
 source common.tcl
 header {C/C++ Interface For SQLite Version 3}
 puts {
@@ -1317,6 +1317,18 @@ api {} {
   by compiling with the SQLITE_ENABLE_MEMORY_MANAGMENT macro.
 }
 
+api {} {
+  void sqlite3_thread_cleanup(void);
+} {
+  This routine ensures that a thread that has used SQLite in the past
+  has released any thread-local storage it might have allocated.  
+  When the rest of the API is used properly, the cleanup of 
+  thread-local storage should be completely automatic.  You should
+  never really need to invoke this API.  But it is provided to you
+  as a precaution and as a potential work-around for future
+  thread-releated memory-leaks.
+}
+
 set n 0
 set i 0
 foreach item $apilist {
@@ -1334,6 +1346,11 @@ foreach name [lsort [array names name_to_idx]] {
   set sname($i) $name
   incr i
 }
+#parray n_to_name
+#parray n_to_idx
+#parray name_to_idx
+#parray sname
+incr n -1
 puts {<table width="100%" cellpadding="5"><tr>}
 set nrow [expr {($n+2)/3}]
 set i 0

www/changes.tcl

@@ -25,6 +25,13 @@ proc chng {date desc} {
   puts "<DD><P><UL>$desc</UL></P></DD>"
 }
 
+chng {2006 January 16 (3.3.1 alpha)} {
+<li>Countless bug fixes</li>
+<li>Speed improvements</li>
+<li>Database connections can now be used by multiple threads, not just
+the thread in which they were created.</li>
+}
+
 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>

www/index.tcl

@@ -66,6 +66,20 @@ proc newsitem {date title text} {
   puts "<hr width=\"50%\">"
 }
 
+newsitem {2006-Jan-16} {Version 3.3.1 alpha} {
+  Many bugs found in last week's alpha release have now been fixed and
+  the library is running much faster again.
+
+  Database connections can now be moved between threads as long as the
+  connection holds no locks at the time it is moved.  Thus the common
+  paradigm of maintaining a pool of database connections and handing
+  them off to transient worker threads is now supported.
+  Please help test this new feature.
+  See <a href="http://www.sqlite.org/cvstrac/wiki?p=MultiThreading">
+  the MultiThreading wiki page</a> for additional
+  information.
+}
+
 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
@@ -135,4 +149,4 @@ puts {
 <p align="right"><a href="oldnews.html">Old news...</a></p>
 </td></tr></table>
 }
-footer {$Id: index.tcl,v 1.129 2006/01/11 01:08:34 drh Exp $}
+footer {$Id: index.tcl,v 1.130 2006/01/15 18:29:18 drh Exp $}