Lines Matching refs:SQLITE_BUSY
775 ** SQLITE_BUSY.
883 #define SQLITE_BUSY 5 /* The database file is locked */
2033 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2039 ** ^If the busy callback is NULL, then [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED]
2048 ** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
2054 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2063 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2069 ** ^The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED]
2077 ** code is promoted from the relatively benign [SQLITE_BUSY] to
2106 ** [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
3338 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
3343 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
3378 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
4272 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
5220 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
5232 ** will always return SQLITE_BUSY. The SQLite core only ever uses
5921 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
5933 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
5981 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
14502 ** thread holds the mutex and it cannot be obtained, return SQLITE_BUSY.
14678 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
14923 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
14954 rc = SQLITE_BUSY;
15183 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
15255 rc = SQLITE_BUSY;
15266 rc = SQLITE_BUSY;
15536 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
15550 int rc = SQLITE_BUSY;
20572 rc = SQLITE_BUSY;
21450 ** a normal expected return code of SQLITE_BUSY or SQLITE_OK
21452 #define IS_LOCK_ERROR(x) ((x != SQLITE_OK) && (x != SQLITE_BUSY))
21890 ** intended to translate a variety of "try again" errors into SQLITE_BUSY
21909 return SQLITE_BUSY;
21917 return SQLITE_BUSY;
22841 rc = SQLITE_BUSY;
22922 rc = SQLITE_BUSY;
23380 rc = SQLITE_BUSY;
23598 rc = SQLITE_BUSY;
23641 r = SQLITE_BUSY;
23769 rc = SQLITE_BUSY;
23882 ** Return SQLITE_OK on success, SQLITE_BUSY on failure.
23910 rc = SQLITE_BUSY;
25961 ** will fail and SQLITE_BUSY is returned.
26272 return SQLITE_BUSY;
26436 rc=SQLITE_CANTOPEN; /* SQLITE_BUSY? proxyTakeConch called
26459 rc = SQLITE_BUSY;
26479 rc = SQLITE_BUSY;
26551 rc=SQLITE_CANTOPEN_BKPT; /* SQLITE_BUSY? proxyTakeConch called
26676 return SQLITE_BUSY;
26743 return SQLITE_BUSY;
28341 rc = SQLITE_BUSY;
29901 if( rc!=SQLITE_OK && rc!=SQLITE_BUSY ){
31649 ** fails, then SQLITE_BUSY may be returned to the user and the user
33696 ** SQLITE_BUSY when trying to upgrade from no-lock to a SHARED lock,
33710 ** retried. If it returns zero, then the SQLITE_BUSY error is
33982 }while( rc==SQLITE_BUSY && pPager->xBusyHandler(pPager->pBusyHandlerArg) );
34246 ** SQLITE_BUSY is returned and no data is written to the database file.
34266 ** be obtained, SQLITE_BUSY is returned.
39997 ** SQLITE_BUSY is returned if the database is locked. SQLITE_NOMEM
40189 ** invoke the busy handler - just return SQLITE_BUSY. SQLITE_BUSY is
40196 ** no progress. By returning SQLITE_BUSY and not invoking the busy callback
40275 }while( rc==SQLITE_BUSY && pBt->inTransaction==TRANS_NONE &&
45872 ** are considered fatal except for SQLITE_BUSY and SQLITE_LOCKED.
45875 return (rc!=SQLITE_OK && rc!=SQLITE_BUSY && ALWAYS(rc!=SQLITE_LOCKED));
45987 ** SQLITE_BUSY immediately.
45990 rc = SQLITE_BUSY;
46238 assert( rc!=SQLITE_BUSY && rc!=SQLITE_LOCKED );
48481 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY || p->rc==SQLITE_NOMEM );
49422 ** lock contention, return SQLITE_BUSY. If SQLITE_BUSY is returned, it
49512 if( rc==SQLITE_BUSY ){
49514 return SQLITE_BUSY;
50926 || rc==SQLITE_BUSY || rc==SQLITE_MISUSE
52533 ** return SQLITE_BUSY.
52983 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY );
53272 assert( rc==SQLITE_BUSY || rc==SQLITE_OK || rc==SQLITE_ERROR );
53273 if( rc==SQLITE_BUSY ){
53274 p->rc = rc = SQLITE_BUSY;
54977 rc = SQLITE_BUSY;
55028 rc = SQLITE_BUSY;
55041 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
55044 p->rc = rc = SQLITE_BUSY;
55122 rc = SQLITE_BUSY;
55129 rc = SQLITE_BUSY;
55139 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
55142 p->rc = rc = SQLITE_BUSY;
55207 if( rc==SQLITE_BUSY ){
55209 p->rc = rc = SQLITE_BUSY;
55382 ** SQLITE_BUSY error code.
95847 ** If lookaside is already active, return SQLITE_BUSY.
95858 return SQLITE_BUSY;
96062 /* If there are any outstanding VMs, return SQLITE_BUSY. */
96064 sqlite3Error(db, SQLITE_BUSY,
96067 return SQLITE_BUSY;
96074 sqlite3Error(db, SQLITE_BUSY,
96077 return SQLITE_BUSY;
96207 /* SQLITE_BUSY */ "database is locked",
96288 ** returns 0, the operation aborts with an SQLITE_BUSY error.
96425 ** and there are active VMs, then return SQLITE_BUSY. If a function
96432 sqlite3Error(db, SQLITE_BUSY,
96435 return SQLITE_BUSY;
96851 sqlite3Error(db, SQLITE_BUSY,
96853 return SQLITE_BUSY;