C API: Prepared Statement Scan Status
(c3ref/c_scanstat_complex.html)
SQLITE_SCANSTAT_COMPLEX
See also lists of
Objects,
Constants, and
Functions.
|
C API: Reset All Bindings On A Prepared Statement
(c3ref/clear_bindings.html)
sqlite3_clear_bindings()
Contrary to the intuition of many, sqlite3_reset() does not reset
the bindings on a prepared statement.
Use this routine to reset all host parameters to NULL.
See also lists of
Objects,
Constants, and
Functions.
|
C API: Query The EXPLAIN Setting For A Prepared Statement
(c3ref/stmt_isexplain.html)
sqlite3_stmt_isexplain()
The sqlite3_stmt_isexplain(S) interface returns 1 if the
prepared statement S is an EXPLAIN statement, or 2 if the
statement S is an EXPLAIN QUERY PLAN.
The sqlite3_stmt_isexplain(S) interface returns 0 if S is
an ordinary statement or a ...
|
C API: Find The Database Handle Of A Prepared Statement
(c3ref/db_handle.html)
sqlite3_db_handle()
The sqlite3_db_handle interface returns the database connection handle
to which a prepared statement belongs. The database connection
returned by sqlite3_db_handle is the same database connection
that was the first argument
to the sqlite3_prepare_v2() call (or its variants) that was used ...
|
C API: Find the next prepared statement
(c3ref/next_stmt.html)
sqlite3_next_stmt()
This interface returns a pointer to the next prepared statement after
pStmt associated with the database connection pDb. If pStmt is NULL
then this interface returns a pointer to the first prepared statement
associated with the database connection pDb. If ...
|
C API: Prepared Statement Status
(c3ref/stmt_status.html)
sqlite3_stmt_status()
Each prepared statement maintains various
SQLITE_STMTSTATUS counters that measure the number
of times it has performed specific operations. These counters can
be used to monitor the performance characteristics of the prepared
statements. For example, if the number of table steps ...
|
C API: Determine If A Prepared Statement Has Been Reset
(c3ref/stmt_busy.html)
sqlite3_stmt_busy()
The sqlite3_stmt_busy(S) interface returns true (non-zero) if the
prepared statement S has been stepped at least once using
sqlite3_step(S) but has neither run to completion (returned
SQLITE_DONE from sqlite3_step(S)) nor
been reset using sqlite3_reset(S). The ...
|
C API: Destroy A Prepared Statement Object
(c3ref/finalize.html)
sqlite3_finalize()
The sqlite3_finalize() function is called to delete a prepared statement.
If the most recent evaluation of the statement encountered no errors
or if the statement is never been evaluated, then sqlite3_finalize() returns
SQLITE_OK. If the most recent evaluation of statement ...
|
C API: Prepared Statement Object
(c3ref/stmt.html)
struct sqlite3_stmt
... A prepared statement object
is the compiled object code. All SQL must be converted into a
prepared statement before it can be run.
The life-cycle of a prepared statement object usually goes like this:
Create the prepared statement object ...
|
C API: Reset A Prepared Statement Object
(c3ref/reset.html)
sqlite3_reset()
The sqlite3_reset() function is called to reset a prepared statement
object back to its initial state, ready to be re-executed.
Any SQL statement variables that had values bound to them using
the sqlite3_bind_*() API retain their values.
Use sqlite3_clear_bindings ...
|
Page generated by FTS5 in about 122.04 ms.