Lines Matching refs:SQLITE_BUSY

309 ** [SQLITE_BUSY]. ^If sqlite3_close_v2() is called with unfinalized prepared
427 #define SQLITE_BUSY 5 /* The database file is locked */
510 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8))
511 #define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY | (2<<8))
512 #define SQLITE_BUSY_TIMEOUT (SQLITE_BUSY | (3<<8))
2096 ** [SQLITE_BUSY].)^</dd>
2613 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2625 ** ^If the busy callback is NULL, then [SQLITE_BUSY]
2634 ** access the database and [SQLITE_BUSY] is returned
2641 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2651 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2682 ** [SQLITE_BUSY].
4649 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
4654 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
4702 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
6137 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
7493 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
7503 ** will always return SQLITE_BUSY. The SQLite core only ever uses
8632 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
8648 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
8696 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
9099 ** lock cannot be obtained and SQLITE_BUSY is returned. ^Even if there is a
9111 ** without blocking any further. ^SQLITE_BUSY is returned in this case.
9117 ** an SQLITE_BUSY error is encountered when processing one or more of the
9119 ** attached databases and SQLITE_BUSY is returned at the end. ^If any other
9122 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached
9440 ** function returns SQLITE_BUSY.
9667 ** database snapshot) if SQLITE_ERROR, SQLITE_BUSY or SQLITE_ERROR_SNAPSHOT
9836 ** The sqlite3_deserialize() interface will fail with SQLITE_BUSY if the