Add an entry to faq.tcl regarding SQLITE_SCHEMA errors. (CVS 2277)

FossilOrigin-Name: 12defe8cd6a0d7434c8f74b88169155d47299079

diff --git a/manifest b/manifest
index 9f31ffe06dd908ed656ebd52ec0788f0e9142225..dcfde2c794f2a2f7028c5f26663160e6740d2f77 100644 (file)
--- a/manifest
+++ b/manifest
@@ -1,5 +1,5 @@
-C Allow\sGROUP\sBY\son\snon-aggregate\squeries.\sTicket\s#1064\s(CVS\s2276)
-D 2005-01-26T03:58:36
+C Add\san\sentry\sto\sfaq.tcl\sregarding\sSQLITE_SCHEMA\serrors.\s(CVS\s2277)
+D 2005-01-26T10:39:58
 F Makefile.in ffd81f5e926d40b457071b4de8d7c1fa18f39b5a
 F Makefile.linux-gcc a9e5a0d309fa7c38e7c14d3ecf7690879d3a5457
 F README a01693e454a00cc117967e3f9fdab2d4d52e9bc1
@@ -251,7 +251,7 @@ F www/different.tcl 051086bc273a36808dc08d58ed098611fb53e315
 F www/docs.tcl 09e5eccffad783fe65fac87772f5265e9bb64abe
 F www/download.tcl 9263a5418c7c0945ff86c1011b8a048f1db3ef2a
 F www/dynload.tcl 02eb8273aa78cfa9070dd4501dca937fb22b466c
-F www/faq.tcl abe360e630d8134bc6242c5e3664969c397eac6e
+F www/faq.tcl 1e348dec52dc0f21f4216fd6918c69c56daa4cfd
 F www/fileformat.tcl 900c95b9633abc3dcfc384d9ddd8eb4876793059
 F www/formatchng.tcl bfbf14dbf5181e771d06da7797767b0200b36d8a
 F www/index.tcl 2ac775d5247922fd0f5d62178b28d41ccaed7d01
@@ -272,7 +272,7 @@ F www/tclsqlite.tcl e73f8f8e5f20e8277619433f7970060ab01088fc
 F www/vdbe.tcl 095f106d93875c94b47367384ebc870517431618
 F www/version3.tcl 092a01f5ef430d2c4acc0ae558d74c4bb89638a0
 F www/whentouse.tcl 3e522a06ad41992023c80ca29a048ae2331ca5bd
-P cabab62bc10568d435806a7059fad7274f0dd4c8
-R ffae8f42ca0f009f38563fe1ef5cdd78
+P 0642d3e3d6636a5f922f75c05252c9c1372d3936
+R ff98b5bb4857d018624b47a08a862aa2
 U danielk1977
-Z d9bb33809efa4982a979cf246654c1ed
+Z 0d80c050a8433757427c9d87cf25f2e2

diff --git a/manifest.uuid b/manifest.uuid
index c2922406f71773e7bf90c10901750a4307cd1e13..76e167835179e31205772aadaf4c2e61b8c6ef1d 100644 (file)
--- a/manifest.uuid
+++ b/manifest.uuid
@@ -1 +1 @@
-0642d3e3d6636a5f922f75c05252c9c1372d3936
\ No newline at end of file
+12defe8cd6a0d7434c8f74b88169155d47299079
\ No newline at end of file

diff --git a/www/faq.tcl b/www/faq.tcl
index 80bf8729d49a6de074dc3c83a9f9b933b25fd018..9ffebb1e613b3a5d8797057f8078bc46ab57e82a 100644 (file)
--- a/www/faq.tcl
+++ b/www/faq.tcl
@@ -1,7 +1,7 @@
 #
 # Run this script to generated a faq.html output file
 #
-set rcsid {$Id: faq.tcl,v 1.27 2004/11/10 05:48:57 danielk1977 Exp $}
+set rcsid {$Id: faq.tcl,v 1.28 2005/01/26 10:39:58 danielk1977 Exp $}
 source common.tcl
 header {SQLite Frequently Asked Questions</title>}
 
@@ -426,6 +426,58 @@ faq {
   </pre></blockquote>
 }
 
+faq {What is an SQLITE_SCHEMA error, and why am I getting one?} {
+  <p>In version 3 of SQLite, an SQLITE_SCHEMA error is returned when a 
+  prepared SQL statement is no longer valid and cannot be executed.
+  When this occurs, the statement must be recompiled from SQL using 
+  the sqlite3_prepare() API. In SQLite 3, an SQLITE_SCHEMA error can
+  only occur when using the sqlite3_prepare()/sqlite3_step()/sqlite3_finalize()
+  API to execute SQL, not when using the sqlite3_exec(). This was not
+  the case in version 2.</p>
+
+  <p>The most common reason for a prepared statement to become invalid
+  is that the schema of the database was modified after the SQL was 
+  prepared (possibly by another process).  The other reasons this can 
+  happen are:</p> 
+  <ul>
+  <li>A database was DETACHed.
+  <li>A user-function definition was deleted or changed.
+  <li>A collation sequence definition was deleted or changed.
+  <li>The authorization function was changed.
+  </ul>
+
+  <p>In all cases, the solution is to recompile the statement from SQL
+  and attempt to execute it again. Because a prepared statement can be
+  invalidated by another process changing the database schema, all code
+  that uses the sqlite3_prepare()/sqlite3_step()/sqlite3_finalize()
+  API should be prepared to handle SQLITE_SCHEMA errors. An example
+  of one approach to this follows:</p>
+
+  <blockquote><pre>
+
+    int rc;
+    sqlite3_stmt *pStmt;
+    char zSql[] = "SELECT .....";
+
+    do {
+      /* Compile the statement from SQL. Assume success. */
+      sqlite3_prepare(pDb, zSql, -1, &pStmt, 0);
+
+      while( SQLITE_ROW==sqlite3_step(pStmt) ){
+        /* Do something with the row of available data */
+      }
+
+      /* Finalize the statement. If an SQLITE_SCHEMA error has
+      ** occured, then the above call to sqlite3_step() will have
+      ** returned SQLITE_ERROR. sqlite3_finalize() will return
+      ** SQLITE_SCHEMA. In this case the loop will execute again.
+      */
+      rc = sqlite3_finalize(pStmt);
+    } while( rc==SQLITE_SCHEMA );
+    
+  </pre></blockquote>
+}
+
 # End of questions and answers.
 #############