Lines Matching defs:SQLITE_BUSY
278 ** will leave the database connection open and return [SQLITE_BUSY].
404 #define SQLITE_BUSY 5 /* The database file is locked */
475 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8))
476 #define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY | (2<<8))
1785 ** [SQLITE_BUSY].)^</dd>
2030 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2040 ** ^If the busy callback is NULL, then [SQLITE_BUSY]
2049 ** access the database and [SQLITE_BUSY] is returned
2056 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2066 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2096 ** [SQLITE_BUSY].
3633 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
3638 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
3685 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
4793 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
5904 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
5916 ** will always return SQLITE_BUSY. The SQLite core only ever uses
6797 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
6813 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
6861 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
7228 ** lock cannot be obtained and SQLITE_BUSY is returned. Even if there is a
7240 ** without blocking any further. SQLITE_BUSY is returned in this case.
7245 ** an SQLITE_BUSY error is encountered when processing one or more of the
7247 ** attached databases and SQLITE_BUSY is returned to the caller. If any other
7250 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached
