Lines Matching defs:SQLITE_BUSY
278 ** SQLITE_BUSY.
386 #define SQLITE_BUSY 5 /* The database file is locked */
459 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8))
1451 ** [SQLITE_BUSY].)^</dd>
1668 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
1674 ** ^If the busy callback is NULL, then [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED]
1683 ** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
1689 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
1698 ** SQLite returns [SQLITE_BUSY
1704 ** ^The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED]
1712 ** code is promoted from the relatively benign [SQLITE_BUSY] to
1741 ** [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
3019 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
3024 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
3067 ** error other than [SQLITE_BUSY
4059 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
5078 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
5090 ** will always return SQLITE_BUSY. The SQLite core only ever uses
5830 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
5846 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
5894 SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
