Lines Matching defs:SQLITE_BUSY
278 ** SQLITE_BUSY.
386 #define SQLITE_BUSY 5 /* The database file is locked */
456 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8))
1485 ** [SQLITE_BUSY].)^</dd>
1724 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
1730 ** ^If the busy callback is NULL, then [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED]
1739 ** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
1745 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
1754 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
1760 ** ^The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED]
1768 ** code is promoted from the relatively benign [SQLITE_BUSY] to
1797 ** [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
3099 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
3104 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
3151 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
4143 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
5162 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
5174 ** will always return SQLITE_BUSY. The SQLite core only ever uses
5941 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
5957 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
6005 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
6345 ** lock cannot be obtained and SQLITE_BUSY is returned. Even if there is a
6357 ** without blocking any further. SQLITE_BUSY is returned in this case.
6362 ** an SQLITE_BUSY error is encountered when processing one or more of the
6364 ** attached databases and SQLITE_BUSY is returned to the caller. If any other
6367 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached