Lines Matching refs:SQLITE_BUSY

251 ** SQLITE_BUSY.
359 #define SQLITE_BUSY         5   /* The database file is locked */
1509 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
1515 ** ^If the busy callback is NULL, then [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED]
1524 ** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
1530 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
1539 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
1545 ** ^The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED]
1553 ** code is promoted from the relatively benign [SQLITE_BUSY] to
1582 ** [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
2814 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
2819 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
2854 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE].  You must call
3748 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
4696 ** SQLITE_BUSY.  ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
4708 ** will always return SQLITE_BUSY.  The SQLite core only ever uses
5397 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
5409 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
5457 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()