Lines Matching refs:sqlite3_step

276 ** [sqlite3_prepare_v2()], [sqlite3_step()], and [sqlite3_finalize()],
381 #define SQLITE_ROW         100  /* sqlite3_step() has another row ready */
382 #define SQLITE_DONE        101  /* sqlite3_step() has finished executing */
1382 ** ^Calling [sqlite3_exec()] or [sqlite3_step()] recursively does
1581 ** the handler returns 0 which causes [sqlite3_step()] to return
1953 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
1957 ** statement might be re-prepared during [sqlite3_step()] due to a 
1959 ** correct authorizer callback remains in place during the [sqlite3_step()].
1963 ** performed during statement evaluation in [sqlite3_step()], unless
1964 ** as stated in the previous paragraph, sqlite3_step() invokes
2047 ** various times when an SQL statement is being run by [sqlite3_step()].
2068 ** running calls to [sqlite3_exec()], [sqlite3_step()] and
2078 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
2241 ** <li> Run the SQL by calling [sqlite3_step()] one or more times.
2381 ** executed using [sqlite3_step()].  ^If there is an error, *ppStmt is set
2396 ** original SQL text. This causes the [sqlite3_step()] interface to
2402 ** always used to do, [sqlite3_step()] will automatically recompile the SQL
2404 ** a way that makes the statement no longer valid, [sqlite3_step()] will still
2412 ** ^When an error occurs, [sqlite3_step()] will return one of the detailed
2414 ** [sqlite3_step()] would only return a generic [SQLITE_ERROR] result code
2424 ** [sqlite3_step()] call following any change to the 
2583 ** [sqlite3_step()] has been called more recently than [sqlite3_reset()],
2807 ** The details of the behavior of the sqlite3_step() interface depend
2827 ** successfully.  sqlite3_step() should not be called again on this virtual
2834 ** sqlite3_step() is called again to retrieve the next row of data.
2837 ** violation) has occurred.  sqlite3_step() should not be called again on
2843 ** the more specific error code is returned directly by sqlite3_step().
2852 ** <b>Goofy Interface Alert:</b> In the legacy interface, the sqlite3_step()
2862 ** by sqlite3_step().  The use of the "v2" interface is recommended.
2864 SQLITE_API int sqlite3_step(sqlite3_stmt*);
2924 ** [sqlite3_step()] has returned [SQLITE_ROW] and neither
2927 ** [sqlite3_finalize()] or after [sqlite3_step()] has returned
2929 ** If [sqlite3_step()] or [sqlite3_reset()] or [sqlite3_finalize()]
3048 ** described above, or until [sqlite3_step()] or [sqlite3_reset()] or
3101 ** ^If the most recent call to [sqlite3_step(S)] for the
3103 ** or if [sqlite3_step(S)] has never before been called on S,
3106 ** ^If the most recent call to [sqlite3_step(S)] for the
3809 ** completion of the [sqlite3_step()] call that triggered the commit
3811 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
3869 ** completion of the [sqlite3_step()] call that triggered the update hook.
3870 ** Note that [sqlite3_prepare_v2()] and [sqlite3_step()] both modify their
5543 ** callback is invoked from within the [sqlite3_step] or [sqlite3_close]
5616 ** When a call to [sqlite3_step()] returns SQLITE_LOCKED, it is almost 
5627 ** by an sqlite3_step() call. ^(If there is a blocking connection, then the