Updated: 2025/Nov/16

Please read Privacy Policy. It's for your privacy.

SQLITE3_STMT_BUSY(3)       Library Functions Manual       SQLITE3_STMT_BUSY(3)

NAME
     sqlite3_stmt_busy - determine if a prepared statement has been reset

SYNOPSIS
     #include <sqlite3.h>

     int
     sqlite3_stmt_busy(sqlite3_stmt*);

DESCRIPTION
     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
     sqlite3_stmt_busy(S) interface returns false if S is a NULL pointer.  If
     S is not a NULL pointer and is not a pointer to a valid prepared
     statement object, then the behavior is undefined and probably
     undesirable.

     This interface can be used in combination sqlite3_next_stmt() to locate
     all prepared statements associated with a database connection that are in
     need of being reset.  This can be used, for example, in diagnostic
     routines to search for prepared statements that are holding a transaction
     open.

IMPLEMENTATION NOTES
     These declarations were extracted from the interface documentation at
     line 4464.

     SQLITE_API int sqlite3_stmt_busy(sqlite3_stmt*);

SEE ALSO
     sqlite3_next_stmt(3), sqlite3_stmt(3), SQLITE_OK(3)

NetBSD 11.99                   January 24, 2024                   NetBSD 11.99