contrib/sqlite3/sqlite3.h

3805 ** <li> Reset the prepared statement using [sqlite3_reset()] then go back
4038 ** and the application would have to make a second call to [sqlite3_reset()]
4205 ** been reset using [sqlite3_reset(S)].  ^The sqlite3_stmt_busy(S)
4391 ** [sqlite3_step()] has been called more recently than [sqlite3_reset()],
4396 ** ^Bindings are not cleared by the [sqlite3_reset()] routine.
4497 ** ^Contrary to the intuition of many, [sqlite3_reset()] does not reset
4663 ** machine without first calling [sqlite3_reset()] to reset the virtual
4676 ** can be obtained by calling [sqlite3_reset()] on the
4688 ** [sqlite3_reset()] was required after sqlite3_step() returned anything
4691 ** [sqlite3_reset()] would result in an [SQLITE_MISUSE] return from
4694 ** calling [sqlite3_reset()] automatically in this circumstance rather
4703 ** [sqlite3_reset()] or [sqlite3_finalize()] in order to find one of the
4808 ** [sqlite3_reset()] nor [sqlite3_finalize()] have been called subsequently.
4809 ** If any of these routines are called after [sqlite3_reset()] or
4812 ** If [sqlite3_step()] or [sqlite3_reset()] or [sqlite3_finalize()]
4951 ** described above, or until [sqlite3_step()] or [sqlite3_reset()] or
5002 ** one or more calls to [sqlite3_reset()], or after any call
5020 ** The sqlite3_reset() function is called to reset a [prepared statement]
5026 ** ^The [sqlite3_reset(S)] interface resets the [prepared statement] S
5032 ** then [sqlite3_reset(S)] returns [SQLITE_OK].
5036 ** [sqlite3_reset(S)] returns an appropriate [error code].
5038 ** ^The [sqlite3_reset(S)] interface does not change the values
5041 SQLITE_API int sqlite3_reset(sqlite3_stmt *pStmt);
5592 ** <li> ^(when [sqlite3_reset()] or [sqlite3_finalize()] is called for the
8301 ** or more calls to [sqlite3_step()] followed by a call to [sqlite3_reset()].
9657 ** to sqlite3_step() but not sqlite3_reset() or sqlite3_finalize()).