database/sqlite
1
0
Fork 0
mirror of https://github.com/sqlite/sqlite.git synced 2026-01-06 08:01:16 +03:00
Code Activity

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

Browse Source 
FossilOrigin-Name: 3b00e769cd30aa50a75f82babb7d2cc90aeb1238
This commit is contained in:
drh
2009-10-20 14:08:41 +00:00
parent c94b859560
commit 4b5af7733c
3 changed files with 27 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/sqlite.h.in
View File

@@ -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: