Lines Matching refs:SQLITE_BUSY
297 ** will leave the database connection open and return [SQLITE_BUSY].
424 #define SQLITE_BUSY 5 /* The database file is locked */
501 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8))
502 #define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY | (2<<8))
1984 ** [SQLITE_BUSY].)^</dd>
2301 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2313 ** ^If the busy callback is NULL, then [SQLITE_BUSY]
2322 ** access the database and [SQLITE_BUSY] is returned
2329 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2339 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2370 ** [SQLITE_BUSY].
4121 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
4126 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
4174 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
5352 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
6580 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
6590 ** will always return SQLITE_BUSY. The SQLite core only ever uses
7502 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
7518 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
7566 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
7969 ** lock cannot be obtained and SQLITE_BUSY is returned. ^Even if there is a
7981 ** without blocking any further. ^SQLITE_BUSY is returned in this case.
7987 ** an SQLITE_BUSY error is encountered when processing one or more of the
7989 ** attached databases and SQLITE_BUSY is returned at the end. ^If any other
7992 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached
8239 ** function returns SQLITE_BUSY.
