Index: www/tclsqlite.tcl
==================================================================
--- www/tclsqlite.tcl
+++ www/tclsqlite.tcl
@@ -1,9 +1,9 @@
 #
 # Run this Tcl script to generate the tclsqlite.html file.
 #
-set rcsid {$Id: tclsqlite.tcl,v 1.14 2005/08/02 17:38:19 drh Exp $}
+set rcsid {$Id: tclsqlite.tcl,v 1.15 2005/09/13 07:00:06 drh Exp $}
 source common.tcl
 header {The Tcl interface to the SQLite library}
 proc METHOD {name text} {
   puts "<a name=\"$name\">\n<h3>The \"$name\" method</h3>\n"
   puts $text
@@ -39,24 +39,31 @@
 way widgets are created in Tk.
 </p>
 
 <p>
 The name of the database is just the name of a disk file in which
-the database is stored.
+the database is stored.  If the name of the database is an empty
+string or the special name ":memory:" then a new database is created
+in memory.
 </p>
 
 <p>
 Once an SQLite database is open, it can be controlled using 
-methods of the <i>dbcmd</i>.  There are currently 19 methods
+methods of the <i>dbcmd</i>.  There are currently 21 methods
 defined:</p>
+
+<p>The <b>sqlite3</b> also accepts an optional third argument called
+the "mode".  This argument is a legacy from SQLite version 2 and is
+currently ignored.</p>
 
 <p>
 <ul>
 }
 foreach m [lsort {
  authorizer
  busy
+ cache
  changes
  close
  collate
  collation_needed
  commit_hook
@@ -83,36 +90,10 @@
 <p>The use of each of these methods will be explained in the sequel, though
 not in the order shown above.</p>
 
 }
 
-##############################################################################
-METHOD close {
-
-<p>
-As its name suggests, the "close" method to an SQLite database just
-closes the database.  This has the side-effect of deleting the
-<i>dbcmd</i> Tcl command.  Here is an example of opening and then
-immediately closing a database:
-</p>
-
-<blockquote>
-<b>sqlite3 db1 ./testdb<br>
-db1 close</b>
-</blockquote>
-
-<p>
-If you delete the <i>dbcmd</i> directly, that has the same effect
-as invoking the "close" method.  So the following code is equivalent
-to the previous:</p>
-
-<blockquote>
-<b>sqlite3 db1 ./testdb<br>
-rename db1 {}</b>
-</blockquote>
-}
-
 ##############################################################################
 METHOD eval {
 <p>
 The most useful <i>dbcmd</i> method is "eval".  The eval method is used
 to execute SQL on the database.  The syntax of the eval method looks
@@ -228,10 +209,36 @@
 technique is not only easier to write, it is also much more efficient
 since it avoids making a copy of the content of $bigblob.
 </p>
 
 }
+
+##############################################################################
+METHOD close {
+
+<p>
+As its name suggests, the "close" method to an SQLite database just
+closes the database.  This has the side-effect of deleting the
+<i>dbcmd</i> Tcl command.  Here is an example of opening and then
+immediately closing a database:
+</p>
+
+<blockquote>
+<b>sqlite3 db1 ./testdb<br>
+db1 close</b>
+</blockquote>
+
+<p>
+If you delete the <i>dbcmd</i> directly, that has the same effect
+as invoking the "close" method.  So the following code is equivalent
+to the previous:</p>
+
+<blockquote>
+<b>sqlite3 db1 ./testdb<br>
+rename db1 {}</b>
+</blockquote>
+}
 
 ##############################################################################
 METHOD transaction {
 
 <p>
@@ -266,10 +273,42 @@
 <p>
 The <i>transaction-type</i> can be one of <b>deferred</b>,
 <b>exclusive</b> or <b>immediate</b>.  The default is deferred.
 </p>
 }
+
+##############################################################################
+METHOD cache {
+
+<p>
+The "eval" method described <a href="#eval">above</a> keeps a cache of
+<a href="capi3ref.html#sqlite3_prepare">prepared statements</a>
+for recently evaluated SQL commands.  
+The "cache" method is used to control this cache.
+The first form of this command is:</p>
+
+<blockquote>
+<i>dbcmd</i>&nbsp;&nbsp;<b>cache size</b>&nbsp;&nbsp;<i>N</i>
+</blockquote>
+
+<p>This sets the maximum number of statements that can be cached.
+The upper limit is 100.  The default is 10.  If you set the cache size
+to 0, no caching is done.</p>
+
+<p>The second form of the command is this:</p>
+
+
+<blockquote>
+<i>dbcmd</i>&nbsp;&nbsp;<b>cache flush</b>
+</blockquote>
+
+<p>The cache-flush method 
+<a href="capi3ref.html#sqlite3_finalize">finalizes</a>
+all prepared statements currently
+in the cache.</p>
+
+}
 
 ##############################################################################
 METHOD complete {
 
 <p>
@@ -277,13 +316,13 @@
 It returns TRUE if the string is a complete statement of SQL and FALSE if
 there is more to be entered.</p>
 
 <p>The "complete" method is useful when building interactive applications
 in order to know when the user has finished entering a line of SQL code.
-This is really just an interface to the <b>sqlite3_complete()</b> C
-function.  Refer to the <a href="c_interface.html">C/C++ interface</a>
-specification for additional information.</p>
+This is really just an interface to the 
+<a href="capi3ref.html#sqlite3_complete"><b>sqlite3_complete()</b></a> C
+function.
 }
 
 ##############################################################################
 METHOD copy {
 
@@ -424,11 +463,12 @@
 
 
 ##############################################################################
 METHOD onecolumn {
 
-<p>The "onecolumn" method works like "eval" in that it evaluates the
+<p>The "onecolumn" method works like 
+"<a href="#eval">eval</a>" in that it evaluates the
 SQL query statement given as its argument.  The difference is that
 "onecolumn" returns a single element which is the first column of the
 first row of the query result.</p>
 
 <p>This is a convenience method.  It saves the user from having to
@@ -453,11 +493,12 @@
 }
 
 ##############################################################################
 METHOD authorizer {
 
-<p>The "authorizer" method provides access to the sqlite3_set_authorizer
+<p>The "authorizer" method provides access to the 
+<a href="capi3ref.html#sqlite3_set_authorizer">sqlite3_set_authorizer</a>
 C/C++ interface.  The argument to authorizer is the name of a procedure that
 is called when SQL statements are being compiled in order to authorize
 certain operations.  The callback procedure takes 5 arguments which describe
 the operation being coded.  If the callback returns the text string
 "SQLITE_OK", then the operation is allowed.  If it returns "SQLITE_IGNORE",