Add requirements marks to the sqlite3_expanded_sql() documentation.

FossilOrigin-Name: 409535e6dfc307f26ea3d9f51be51c439b6d7b22
This commit is contained in:
drh
2016-07-22 20:20:53 +00:00
parent 8d85364261
commit dec8bc0eb4
3 changed files with 11 additions and 11 deletions
+4 -4
View File
@@ -3503,14 +3503,14 @@ int sqlite3_prepare16_v2(
** string containing the SQL text of prepared statement P with
** [bound parameters] expanded.
**
** For example, if a prepared statement is created using the SQL
** ^(For example, if a prepared statement is created using the SQL
** text "SELECT $abc,:xyz" and if parameter $abc is bound to integer 2345
** and parameter :xyz is unbound, then sqlite3_sql() will return
** the original string, "SELECT $abc,:xyz" but sqlite3_expanded_sql()
** will return "SELECT 2345,NULL".
** will return "SELECT 2345,NULL".)^
**
** The [SQLITE_TRACE_SIZE_LIMIT] setting limits the size of a
** bound parameter expansion. If SQLite is built with the
** ^The [SQLITE_TRACE_SIZE_LIMIT] setting limits the size of a
** bound parameter expansion. ^If SQLite is built with the
** [SQLITE_OMIT_TRACE] compile-time option then the sqlite3_expanded_sql()
** interface is non-functional and always returns NULL.
**