contrib/sqlite3/sqlite3.h

278 ** will leave the database connection open and return [SQLITE_BUSY].
406 #define SQLITE_BUSY         5   /* The database file is locked */
482 #define SQLITE_BUSY_RECOVERY           (SQLITE_BUSY   |  (1<<8))
1734 ** [SQLITE_BUSY].)^</dd>
1977 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
1983 ** ^If the busy callback is NULL, then [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED]
1992 ** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
1998 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2007 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2013 ** ^The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED]
2021 ** code is promoted from the relatively benign [SQLITE_BUSY] to
2050 ** [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
3557 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
3562 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
3609 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE].  You must call
4668 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
5745 ** SQLITE_BUSY.  ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
5757 ** will always return SQLITE_BUSY.  The SQLite core only ever uses
6614 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
6630 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
6678 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
7035 ** lock cannot be obtained and SQLITE_BUSY is returned. Even if there is a
7047 ** without blocking any further. SQLITE_BUSY is returned in this case.
7052 ** an SQLITE_BUSY error is encountered when processing one or more of the
7054 ** attached databases and SQLITE_BUSY is returned to the caller. If any other
7057 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached