Lines Matching refs:SQLITE_BUSY
574 ** will leave the database connection open and return [SQLITE_BUSY].
701 #define SQLITE_BUSY 5 /* The database file is locked */
778 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8))
779 #define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY | (2<<8))
2261 ** [SQLITE_BUSY].)^</dd>
2578 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2590 ** ^If the busy callback is NULL, then [SQLITE_BUSY]
2599 ** access the database and [SQLITE_BUSY] is returned
2606 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2616 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2647 ** [SQLITE_BUSY].
4398 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
4403 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
4451 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
5629 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
6857 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
6867 ** will always return SQLITE_BUSY. The SQLite core only ever uses
7779 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
7795 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
7843 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
8246 ** lock cannot be obtained and SQLITE_BUSY is returned. ^Even if there is a
8258 ** without blocking any further. ^SQLITE_BUSY is returned in this case.
8264 ** an SQLITE_BUSY error is encountered when processing one or more of the
8266 ** attached databases and SQLITE_BUSY is returned at the end. ^If any other
8269 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached
8516 ** function returns SQLITE_BUSY.
22932 ** thread holds the mutex and it cannot be obtained, return SQLITE_BUSY.
23130 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
23429 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
23504 rc = SQLITE_BUSY;
23517 rc = SQLITE_BUSY;
24149 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
24183 int rc = SQLITE_BUSY;
29922 ** a normal expected return code of SQLITE_BUSY or SQLITE_OK
29924 #define IS_LOCK_ERROR(x) ((x != SQLITE_OK) && (x != SQLITE_BUSY))
30754 ** intended to translate a variety of "try again" errors into SQLITE_BUSY
30775 return SQLITE_BUSY;
31549 rc = SQLITE_BUSY;
31583 if( rc!=SQLITE_BUSY ){
31618 if( rc!=SQLITE_BUSY ){
31630 rc = SQLITE_BUSY;
31651 if( rc!=SQLITE_BUSY ){
31812 ** SQLITE_BUSY would confuse the upper layer (in practice it causes
32107 rc = SQLITE_BUSY;
32110 if( rc!=SQLITE_BUSY ){
32330 rc = SQLITE_BUSY;
32489 rc = SQLITE_BUSY;
32601 ** Return SQLITE_OK on success, SQLITE_BUSY on failure.
32629 rc = SQLITE_BUSY;
32760 rc = SQLITE_BUSY;
32834 rc = SQLITE_BUSY;
34110 rc = (rc!=(-1)) ? SQLITE_OK : SQLITE_BUSY;
34576 ** SQLITE_BUSY.
34580 rc = SQLITE_BUSY;
34601 ** lock. If any do, return SQLITE_BUSY right away.
34605 rc = SQLITE_BUSY;
36417 ** will fail and SQLITE_BUSY is returned.
36620 return SQLITE_BUSY;
36784 if( rc==SQLITE_BUSY ){
36806 return SQLITE_BUSY;
36819 return SQLITE_BUSY;
36823 return SQLITE_BUSY;
36840 } while( rc==SQLITE_BUSY && nTries<3 );
36935 rc = SQLITE_BUSY;
36955 rc = SQLITE_BUSY;
37024 rc=SQLITE_CANTOPEN_BKPT; /* SQLITE_BUSY? proxyTakeConch called
37146 return SQLITE_BUSY;
37214 return SQLITE_BUSY;
39120 ** the sqlite3_memory_used() function does not return zero, SQLITE_BUSY will
39155 rc = SQLITE_BUSY;
41131 rc = SQLITE_BUSY;
41568 rc = SQLITE_BUSY;
41842 ** SQLITE_BUSY.
41846 rc = SQLITE_BUSY;
41867 ** lock. If any do, return SQLITE_BUSY right away.
41871 rc = SQLITE_BUSY;
44676 if( rc!=SQLITE_OK && rc!=SQLITE_BUSY ){
47393 ** If the VFS xLock() or xUnlock() returns an error other than SQLITE_BUSY
50703 ** SQLITE_BUSY when trying to upgrade from no-lock to a SHARED lock,
50717 ** retried. If it returns zero, then the SQLITE_BUSY error is
50951 }while( rc==SQLITE_BUSY && pPager->xBusyHandler(pPager->pBusyHandlerArg) );
51363 ** SQLITE_BUSY is returned and no data is written to the database file.
51383 ** be obtained, SQLITE_BUSY is returned.
53308 ** Otherwise, either SQLITE_BUSY or an SQLITE_IOERR_XXX error code is
54544 ** error (SQLITE_BUSY) is returned and the log connection is not closed.
55453 VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && rc!=SQLITE_BUSY); )
55469 VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && rc!=SQLITE_BUSY); )
55729 ** the necessary locks, this routine returns SQLITE_BUSY.
56294 }while( xBusy && rc==SQLITE_BUSY && xBusy(pBusyArg) );
56429 }else if( rc==SQLITE_BUSY ){
56503 if( rc==SQLITE_BUSY ){
56518 rc = SQLITE_BUSY;
56785 ** I/O error or an SQLITE_BUSY because another process is running
56868 if( rc==SQLITE_BUSY ){
56878 /* This branch is taken when the xShmMap() method returns SQLITE_BUSY.
56881 ** modules may return SQLITE_BUSY due to a race condition in the
56889 }else if( rc==SQLITE_BUSY ){
56930 }else if( rc!=SQLITE_BUSY ){
56966 }else if( rc!=SQLITE_BUSY ){
56972 assert( rc==SQLITE_BUSY || (pWal->readOnly & WAL_SHM_RDONLY)!=0 );
56973 return rc==SQLITE_BUSY ? WAL_RETRY : SQLITE_READONLY_CANTLOCK;
56978 return rc==SQLITE_BUSY ? WAL_RETRY : rc;
57135 testcase( (rc&0xff)==SQLITE_BUSY );
57365 ** returns SQLITE_BUSY in that case and no write transaction is started.
57382 ** SQLITE_BUSY if unable.
57543 }else if( rc!=SQLITE_BUSY ){
57554 assert( (rc&0xff)!=SQLITE_BUSY ); /* BUSY not possible when useWal==1 */
57960 ** SQLITE_BUSY is returned.
57964 testcase( rc==SQLITE_BUSY );
57983 }else if( rc==SQLITE_BUSY ){
58008 if( rc==SQLITE_OK || rc==SQLITE_BUSY ){
58029 return (rc==SQLITE_OK && eMode!=eMode2 ? SQLITE_BUSY : rc);
62101 ** SQLITE_BUSY is returned if the database is locked. SQLITE_NOMEM
62401 ** invoke the busy handler - just return SQLITE_BUSY. SQLITE_BUSY is
62408 ** no progress. By returning SQLITE_BUSY and not invoking the busy callback
62494 }while( (rc&0xFF)==SQLITE_BUSY && pBt->inTransaction==TRANS_NONE &&
69284 ** are considered fatal except for SQLITE_BUSY and SQLITE_LOCKED.
69287 return (rc!=SQLITE_OK && rc!=SQLITE_BUSY && ALWAYS(rc!=SQLITE_LOCKED));
69440 ** SQLITE_BUSY immediately.
69443 rc = SQLITE_BUSY;
69776 assert( rc!=SQLITE_BUSY && rc!=SQLITE_LOCKED );
73207 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY || p->rc==SQLITE_NOMEM );
74014 assert( rc!=SQLITE_BUSY );
74187 ** lock contention, return SQLITE_BUSY. If SQLITE_BUSY is returned, it
74291 if( rc==SQLITE_BUSY && p->readOnly ){
74293 return SQLITE_BUSY;
74383 return (p->rc==SQLITE_BUSY ? SQLITE_BUSY : SQLITE_OK);
76807 ** or SQLITE_BUSY error.
76810 if( (rc = p->rc&0xff)==SQLITE_BUSY || rc==SQLITE_LOCKED ){
76899 || (rc&0xff)==SQLITE_BUSY || rc==SQLITE_MISUSE
79055 assert( p->rc==SQLITE_OK || (p->rc&0xff)==SQLITE_BUSY );
79452 assert( rc==SQLITE_BUSY || rc==SQLITE_OK || rc==SQLITE_ERROR );
79453 if( rc==SQLITE_BUSY ){
79454 p->rc = SQLITE_BUSY;
81437 rc = SQLITE_BUSY;
81495 rc = SQLITE_BUSY;
81508 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
81511 p->rc = rc = SQLITE_BUSY;
81610 rc = SQLITE_BUSY;
81617 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
81620 p->rc = rc = SQLITE_BUSY;
81697 if( (rc&0xff)==SQLITE_BUSY ){
81855 ** SQLITE_BUSY error code.
84808 ** SQLITE_BUSY or not, respectively. Write the number of pages in the
84829 if( rc!=SQLITE_BUSY ) goto abort_due_to_error;
141266 ** If lookaside is already active, return SQLITE_BUSY.
141278 return SQLITE_BUSY;
141386 if( rc==SQLITE_BUSY ){
141394 return ((rc==SQLITE_OK && bSeenBusy) ? SQLITE_BUSY : rc);
141687 ** SQLITE_BUSY if the connection can not be closed immediately.
141690 sqlite3ErrorWithMsg(db, SQLITE_BUSY, "unable to close due to unfinalized "
141693 return SQLITE_BUSY;
141712 ** connection. The sqlite3_close() version returns SQLITE_BUSY and
141915 case SQLITE_BUSY: zName = "SQLITE_BUSY"; break;
142019 /* SQLITE_BUSY */ "database is locked",
142109 ** returns 0, the operation aborts with an SQLITE_BUSY error.
142271 ** and there are active VMs, then return SQLITE_BUSY. If a function
142278 sqlite3ErrorWithMsg(db, SQLITE_BUSY,
142281 return SQLITE_BUSY;
142785 int bBusy = 0; /* True if SQLITE_BUSY has been encountered */
142796 if( rc==SQLITE_BUSY ){
142803 return (rc==SQLITE_OK && bBusy) ? SQLITE_BUSY : rc;
142989 sqlite3ErrorWithMsg(db, SQLITE_BUSY,
142991 return SQLITE_BUSY;
169162 ** the suspended RBU update is also an error (SQLITE_BUSY).
171973 ** the checkpoint fails with SQLITE_BUSY (normally SQLite would
171989 ** As a result, unless an error (i.e. OOM or SQLITE_BUSY) occurs, the
172045 pRbu->rc = SQLITE_BUSY;
172997 p->rc = SQLITE_BUSY;
173341 ** fails with an SQLITE_BUSY error. This is to stop RBU connections
173586 rc = SQLITE_BUSY;
173699 if( ofst==WAL_LOCK_CKPT && n==1 ) rc = SQLITE_BUSY;
