Lines Matching full:sqlite3_step
303 ** [sqlite3_prepare_v2()], [sqlite3_step()], and [sqlite3_finalize()],
411 #define SQLITE_ROW 100 /* sqlite3_step() has another row ready */
412 #define SQLITE_DONE 101 /* sqlite3_step() has finished executing */
1541 ** ^Calling [sqlite3_exec()] or [sqlite3_step()] recursively does
1740 ** the handler returns 0 which causes [sqlite3_step()] to return
2117 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
2121 ** statement might be re-prepared during [sqlite3_step()] due to a
2123 ** correct authorizer callback remains in place during the [sqlite3_step()].
2127 ** performed during statement evaluation in [sqlite3_step()], unless
2128 ** as stated in the previous paragraph, sqlite3_step() invokes
2210 ** various times when an SQL statement is being run by [sqlite3_step()].
2237 ** [sqlite3_exec()], [sqlite3_step()] and [sqlite3_get_table()] for
2258 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
2421 ** <li> Run the SQL by calling [sqlite3_step()] one or more times.
2567 ** executed using [sqlite3_step()]. ^If there is an error, *ppStmt is set
2582 ** original SQL text. This causes the [sqlite3_step()] interface to
2588 ** always used to do, [sqlite3_step()] will automatically recompile the SQL
2593 ** ^When an error occurs, [sqlite3_step()] will return one of the detailed
2595 ** [sqlite3_step()] would only return a generic [SQLITE_ERROR] result code
2605 ** a schema change, on the first [sqlite3_step()] call following any change
2786 ** [sqlite3_step()] has been called more recently than [sqlite3_reset()],
3012 ** The details of the behavior of the sqlite3_step() interface depend
3032 ** successfully. sqlite3_step() should not be called again on this virtual
3039 ** sqlite3_step() is called again to retrieve the next row of data.
3042 ** violation) has occurred. sqlite3_step() should not be called again on
3048 ** the more specific error code is returned directly by sqlite3_step().
3058 ** after sqlite3_step() returned anything other than [SQLITE_ROW] that
3060 ** sqlite3_step(). Failure to invoke [sqlite3_reset()] in this way would
3061 ** result in an [SQLITE_MISUSE] return from sqlite3_step(). But after
3062 ** version 3.6.23.1, sqlite3_step() began calling [sqlite3_reset()]
3065 ** <b>Goofy Interface Alert:</b> In the legacy interface, the sqlite3_step()
3075 ** by sqlite3_step(). The use of the "v2" interface is recommended.
3077 SQLITE_API int sqlite3_step(sqlite3_stmt*);
3143 ** [sqlite3_step()] has returned [SQLITE_ROW] and neither
3146 ** [sqlite3_finalize()] or after [sqlite3_step()] has returned
3148 ** If [sqlite3_step()] or [sqlite3_reset()] or [sqlite3_finalize()]
3275 ** described above, or until [sqlite3_step()] or [sqlite3_reset()] or
3312 ** to [sqlite3_step()] regardless of whether or not the statement has
3337 ** ^If the most recent call to [sqlite3_step(S)] for the
3339 ** or if [sqlite3_step(S)] has never before been called on S,
3342 ** ^If the most recent call to [sqlite3_step(S)] for the
4120 ** completion of the [sqlite3_step()] call that triggered the commit
4122 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step
4178 ** completion of the [sqlite3_step()] call that triggered the update hook.
4179 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
5979 ** callback is invoked from within the [sqlite3_step] or [sqlite3_close]
6052 ** When a call to [sqlite3_step()] returns SQLITE_LOCKED, it is almost
6063 ** by an sqlite3_step() call. ^(If there is a blocking connection, then the
