Update documentation on the sqlite3_prepare_v2() interface. No changes to code.

FossilOrigin-Name: 3b00e769cd30aa50a75f82babb7d2cc90aeb1238

diff --git a/manifest b/manifest
index d5368ff567d92a876634fae1f82571977675b91f..8e173987d9f5e433e55cea8e27f3da0211447161 100644 (file)
--- a/manifest
+++ b/manifest
@@ -1,5 +1,8 @@
-C Fix\scases\swhere\smodifying\sbound\svariables\susing\sthe\sclear_bindings()\sor\stransfer_bindings()\sAPIs\scan\sinvalidate\sa\squery\splan.
-D 2009-10-20T07:01:24
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+C Update\sdocumentation\son\sthe\ssqlite3_prepare_v2()\sinterface.\s\sNo\schanges\sto\scode.
+D 2009-10-20T14:08:41
 F Makefile.arm-wince-mingw32ce-gcc fcd5e9cd67fe88836360bb4f9ef4cb7f8e2fb5a0
 F Makefile.in 4ca3f1dd6efa2075bcb27f4dc43eef749877740d
 F Makefile.linux-gcc d53183f4aa6a9192d249731c90dbdffbd2c68654
@@ -162,7 +165,7 @@ F src/resolve.c 3ac31c7181fab03732125fdedf7c2091a5c07f1b
 F src/rowset.c c64dafba1f9fd876836c8db8682966b9d197eb1f
 F src/select.c cbe366a0ce114856e66f5daf0f848d7c48a88298
 F src/shell.c 270231b3f587f1f86391b9994fdfcd5d472c3fdf
-F src/sqlite.h.in 8e1ccddb12b5e983d0a17e1f1477c72b0a72dd84
+F src/sqlite.h.in 70f6e015541bcfeba36217d2a446d442c4b2bb7e
 F src/sqlite3ext.h 1db7d63ab5de4b3e6b83dd03d1a4e64fef6d2a17
 F src/sqliteInt.h 3b00a3ce79e60c5a47c342b738c8b75013f3ec84
 F src/sqliteLimit.h 38b2fffcd01faeaeaadea71b2b47695a81580c8b
@@ -760,7 +763,14 @@ F tool/speedtest2.tcl ee2149167303ba8e95af97873c575c3e0fab58ff x
 F tool/speedtest8.c 2902c46588c40b55661e471d7a86e4dd71a18224
 F tool/speedtest8inst1.c 293327bc76823f473684d589a8160bde1f52c14e
 F tool/vdbe-compress.tcl d70ea6d8a19e3571d7ab8c9b75cba86d1173ff0f x
-P 3bcd78a1d76897d1bd5ad4cea52c6a65612ce433
-R 1728941566ef8ddd5fc7b46882d4b01c
-U dan
-Z 9100d3d85f3bd8c3f556c00cc5107446
+P e6808c988c9cd7b2db23f18b5fe2177151b6f586
+R 1743bc5a2c152c132cb56c70ded214d1
+U drh
+Z c2bea7e2f2a825fe8afec164719785b0
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.6 (GNU/Linux)
+
+iD8DBQFK3cRuoxKgR168RlERAod3AJ0SCMutV1PpGn8gnZMm14r/WylWdwCeOF+K
+B6YXm9KSWW2Nt1qC6l0Y3Ls=
+=lmXW
+-----END PGP SIGNATURE-----

diff --git a/manifest.uuid b/manifest.uuid
index 21b7d55391106942c77c3104d574ec82504d9ad5..53c02f72699abf97d0c0963233d82bfd0e3c72cb 100644 (file)
--- a/manifest.uuid
+++ b/manifest.uuid
@@ -1 +1 @@
-e6808c988c9cd7b2db23f18b5fe2177151b6f586
\ No newline at end of file
+3b00e769cd30aa50a75f82babb7d2cc90aeb1238
\ No newline at end of file

diff --git a/src/sqlite.h.in b/src/sqlite.h.in
index 877c2c7f286f34907e98910b2033fd6a53a98668..8222fd3659e43e5a2be7e2820019c3b687df6d3b 100644 (file)
--- a/src/sqlite.h.in
+++ b/src/sqlite.h.in
@@ -2391,7 +2391,7 @@ int sqlite3_limit(sqlite3*, int id, int newVal);
 ** In the "v2" interfaces, the prepared statement
 ** that is returned (the [sqlite3_stmt] object) contains a copy of the
 ** original SQL text. This causes the [sqlite3_step()] interface to
-** behave a differently in two ways:
+** behave a differently in three ways:
 **
 ** <ol>
 ** <li>
@@ -2413,6 +2413,14 @@ int sqlite3_limit(sqlite3*, int id, int newVal);
 ** to find the underlying cause of the problem. With the "v2" prepare
 ** interfaces, the underlying reason for the error is returned immediately.
 ** </li>
+**
+** <li>
+** ^If the value of a [parameter | host parameter] in the WHERE clause might
+** change the query plan for a statement, then the statement may be
+** automatically recompiled (as if there had been a schema change) on the first 
+** [sqlite3_step()] call following any change to the 
+** [sqlite3_bind_text | bindings] of the [parameter]. 
+** </li>
 ** </ol>
 **
 ** Requirements: