Lines Matching defs:SQLITE_BUSY
645 ** [SQLITE_BUSY]. ^If sqlite3_close_v2() is called with unfinalized prepared
765 #define SQLITE_BUSY 5 /* The database file is locked */
849 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8))
850 #define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY | (2<<8))
851 #define SQLITE_BUSY_TIMEOUT (SQLITE_BUSY | (3<<8))
2543 ** [SQLITE_BUSY].)^</dd>
3113 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
3125 ** ^If the busy callback is NULL, then [SQLITE_BUSY]
3134 ** access the database and [SQLITE_BUSY] is returned
3141 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
3151 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
3182 ** [SQLITE_BUSY].
5253 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
5258 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
5306 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
5653 ** might return SQLITE_BUSY if locking constraints prevent the
6898 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
8370 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
8380 ** will always return SQLITE_BUSY. In most cases the SQLite core only uses
9528 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
9544 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
9592 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
9996 ** lock cannot be obtained and SQLITE_BUSY is returned. ^Even if there is a
10008 ** without blocking any further. ^SQLITE_BUSY is returned in this case.
10014 ** an SQLITE_BUSY error is encountered when processing one or more of the
10016 ** attached databases and SQLITE_BUSY is returned at the end. ^If any other
10019 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached
10661 ** function returns SQLITE_BUSY.
10902 ** database snapshot) if SQLITE_ERROR, SQLITE_BUSY or SQLITE_ERROR_SNAPSHOT
11081 ** The sqlite3_deserialize() interface will fail with SQLITE_BUSY if the
29064 ** thread holds the mutex and it cannot be obtained, return SQLITE_BUSY.
29262 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
29568 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
29643 rc = SQLITE_BUSY;
29656 rc = SQLITE_BUSY;
30090 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
30124 int rc = SQLITE_BUSY;
38588 ** a normal expected return code of SQLITE_BUSY or SQLITE_OK
38590 #define IS_LOCK_ERROR(x) ((x != SQLITE_OK) && (x != SQLITE_BUSY))
39261 ** intended to translate a variety of "try again" errors into SQLITE_BUSY
39282 return SQLITE_BUSY;
40150 rc = SQLITE_BUSY;
40184 if( rc!=SQLITE_BUSY ){
40222 if( rc!=SQLITE_BUSY ){
40234 rc = SQLITE_BUSY;
40255 if( rc!=SQLITE_BUSY ){
40413 ** SQLITE_BUSY would confuse the upper layer (in practice it causes
40715 rc = SQLITE_BUSY;
40718 if( rc!=SQLITE_BUSY ){
40938 rc = SQLITE_BUSY;
41097 rc = SQLITE_BUSY;
41210 ** Return SQLITE_OK on success, SQLITE_BUSY on failure.
41238 rc = SQLITE_BUSY;
41368 rc = SQLITE_BUSY;
41442 rc = SQLITE_BUSY;
42837 rc = (pFile->iBusyTimeout ? SQLITE_BUSY_TIMEOUT : SQLITE_BUSY);
42839 rc = SQLITE_BUSY;
42948 ** return SQLITE_BUSY to the caller (it will try again). An earlier
42990 rc = SQLITE_BUSY;
43444 ** therefore return SQLITE_BUSY to the caller.
43504 rc = SQLITE_BUSY;
43523 ** lock. If any do, return SQLITE_BUSY right away. */
43526 rc = SQLITE_BUSY;
45419 ** will fail and SQLITE_BUSY is returned.
45622 return SQLITE_BUSY;
45786 if( rc==SQLITE_BUSY ){
45808 return SQLITE_BUSY;
45821 return SQLITE_BUSY;
45825 return SQLITE_BUSY;
45842 } while( rc==SQLITE_BUSY && nTries<3 );
45937 rc = SQLITE_BUSY;
45957 rc = SQLITE_BUSY;
46026 rc=SQLITE_CANTOPEN_BKPT; /* SQLITE_BUSY? proxyTakeConch called
46148 return SQLITE_BUSY;
46216 return SQLITE_BUSY;
47939 ** the sqlite3_memory_used() function does not return zero, SQLITE_BUSY will
47974 rc = SQLITE_BUSY;
50022 rc = SQLITE_BUSY;
50472 rc = SQLITE_BUSY;
50777 ** SQLITE_BUSY.
50781 rc = SQLITE_BUSY;
50802 ** lock. If any do, return SQLITE_BUSY right away.
50806 rc = SQLITE_BUSY;
53251 rc = SQLITE_BUSY;
53263 rc = SQLITE_BUSY;
53275 rc = SQLITE_BUSY;
54701 if( rc!=SQLITE_OK && rc!=SQLITE_BUSY ){
57474 ** If the VFS xLock() or xUnlock() returns an error other than SQLITE_BUSY
60790 ** SQLITE_BUSY when trying to upgrade from no-lock to a SHARED lock,
60804 ** retried. If it returns zero, then the SQLITE_BUSY error is
61045 }while( rc==SQLITE_BUSY && pPager->xBusyHandler(pPager->pBusyHandlerArg) );
61488 ** SQLITE_BUSY is returned and no data is written to the database file.
61508 ** be obtained, SQLITE_BUSY is returned.
63500 ** Otherwise, either SQLITE_BUSY or an SQLITE_IOERR_XXX error code is
64742 ** error (SQLITE_BUSY) is returned and the log connection is not closed.
64862 ** the CHECKPOINTER lock cannot be obtained, SQLITE_BUSY. If any error
65989 VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && (rc&0xFF)!=SQLITE_BUSY); )
66011 VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && (rc&0xFF)!=SQLITE_BUSY); )
66285 ** the necessary locks, this routine returns SQLITE_BUSY.
66489 }else if( rc!=SQLITE_BUSY ){
67015 }while( xBusy && rc==SQLITE_BUSY && xBusy(pBusyArg) );
67019 rc = SQLITE_BUSY;
67142 }else if( rc==SQLITE_BUSY ){
67230 if( rc==SQLITE_BUSY ){
67246 rc = SQLITE_BUSY;
67689 if( rc==SQLITE_BUSY ) rc = WAL_RETRY;
67853 ** I/O error or an SQLITE_BUSY because another process is running
67968 rc = SQLITE_BUSY;
67972 if( rc==SQLITE_BUSY ){
67982 /* This branch is taken when the xShmMap() method returns SQLITE_BUSY.
67985 ** modules may return SQLITE_BUSY due to a race condition in the
67993 }else if( rc==SQLITE_BUSY ){
68039 }else if( rc!=SQLITE_BUSY ){
68076 }else if( rc!=SQLITE_BUSY ){
68082 assert( rc==SQLITE_BUSY || (pWal->readOnly & WAL_SHM_RDONLY)!=0 );
68083 return rc==SQLITE_BUSY ? WAL_RETRY : SQLITE_READONLY_CANTINIT;
68097 assert( (rc&0xFF)!=SQLITE_BUSY||rc==SQLITE_BUSY||rc==SQLITE_BUSY_TIMEOUT );
68098 return (rc&0xFF)==SQLITE_BUSY ? WAL_RETRY : rc;
68288 testcase( (rc&0xff)==SQLITE_BUSY );
68563 ** returns SQLITE_BUSY in that case and no write transaction is started.
68590 ** SQLITE_BUSY if unable.
68762 }else if( rc!=SQLITE_BUSY ){
68773 assert( (rc&0xff)!=SQLITE_BUSY ); /* BUSY not possible when useWal==1 */
69200 ** SQLITE_BUSY is returned.
69205 testcase( rc==SQLITE_BUSY );
69223 }else if( rc==SQLITE_BUSY ){
69257 if( rc==SQLITE_OK || rc==SQLITE_BUSY ){
69287 if( rc==SQLITE_BUSY_TIMEOUT ) rc = SQLITE_BUSY;
69289 return (rc==SQLITE_OK && eMode!=eMode2 ? SQLITE_BUSY : rc);
69438 ** the CHECKPOINTER lock cannot be obtained, SQLITE_BUSY. If any error
73807 ** SQLITE_BUSY is returned if the database is locked. SQLITE_NOMEM
74115 ** invoke the busy handler - just return SQLITE_BUSY. SQLITE_BUSY is
74122 ** no progress. By returning SQLITE_BUSY and not invoking the busy callback
74204 if( rc!=SQLITE_BUSY && rc!=SQLITE_OK ) break;
74227 ** code to SQLITE_BUSY. */
74228 rc = SQLITE_BUSY;
74237 }while( (rc&0xFF)==SQLITE_BUSY && pBt->inTransaction==TRANS_NONE &&
74241 if( rc==SQLITE_BUSY_TIMEOUT ) rc = SQLITE_BUSY;
82227 ** are considered fatal except for SQLITE_BUSY and SQLITE_LOCKED.
82230 return (rc!=SQLITE_OK && rc!=SQLITE_BUSY && ALWAYS(rc!=SQLITE_LOCKED));
82350 ** SQLITE_BUSY immediately.
82353 rc = SQLITE_BUSY;
82691 assert( rc!=SQLITE_BUSY && rc!=SQLITE_LOCKED );
87234 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY || p->rc==SQLITE_NOMEM );
87941 assert( rc!=SQLITE_BUSY );
88115 ** lock contention, return SQLITE_BUSY. If SQLITE_BUSY is returned, it
88226 if( rc==SQLITE_BUSY && p->readOnly ){
88228 return SQLITE_BUSY;
88319 return (p->rc==SQLITE_BUSY ? SQLITE_BUSY : SQLITE_OK);
91196 ** or SQLITE_BUSY error.
91199 if( (rc = p->rc&0xff)==SQLITE_BUSY || rc==SQLITE_LOCKED ){
91262 || (rc&0xff)==SQLITE_BUSY || rc==SQLITE_MISUSE
92377 rc = SQLITE_BUSY;
93966 assert( p->rc==SQLITE_OK || (p->rc&0xff)==SQLITE_BUSY );
94415 assert( rc==SQLITE_BUSY || rc==SQLITE_OK || rc==SQLITE_ERROR );
94416 if( rc==SQLITE_BUSY ){
94417 p->rc = SQLITE_BUSY;
96876 rc = SQLITE_BUSY;
96935 rc = SQLITE_BUSY;
96948 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
96951 p->rc = rc = SQLITE_BUSY;
97060 rc = SQLITE_BUSY;
97067 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
97070 p->rc = rc = SQLITE_BUSY;
97157 if( (rc&0xff)==SQLITE_BUSY ){
100931 ** SQLITE_BUSY or not, respectively. Write the number of pages in the
100952 if( rc!=SQLITE_BUSY ) goto abort_due_to_error;
180547 ** If lookaside is already active, return SQLITE_BUSY.
180563 return SQLITE_BUSY;
180709 if( rc==SQLITE_BUSY ){
180717 return ((rc==SQLITE_OK && bSeenBusy) ? SQLITE_BUSY : rc);
181043 ** SQLITE_BUSY if the connection can not be closed immediately.
181046 sqlite3ErrorWithMsg(db, SQLITE_BUSY, "unable to close due to unfinalized "
181049 return SQLITE_BUSY;
181106 ** connection. The sqlite3_close() version returns SQLITE_BUSY and
181310 case SQLITE_BUSY: zName = "SQLITE_BUSY"; break;
181417 /* SQLITE_BUSY */ "database is locked",
181478 ** and cause SQLite to return SQLITE_BUSY.
181530 ** returns 0, the operation aborts with an SQLITE_BUSY error.
181734 ** and there are active VMs, then return SQLITE_BUSY. If a function
181741 sqlite3ErrorWithMsg(db, SQLITE_BUSY,
181744 return SQLITE_BUSY;
182359 int bBusy = 0; /* True if SQLITE_BUSY has been encountered */
182372 if( rc==SQLITE_BUSY ){
182379 return (rc==SQLITE_OK && bBusy) ? SQLITE_BUSY : rc;
182575 sqlite3ErrorWithMsg(db, SQLITE_BUSY,
182577 return SQLITE_BUSY;
217836 ** the suspended RBU update is also an error (SQLITE_BUSY).
221141 ** the checkpoint fails with SQLITE_BUSY (normally SQLite would
221157 ** As a result, unless an error (i.e. OOM or SQLITE_BUSY) occurs, the
221213 pRbu->rc = SQLITE_BUSY;
222193 p->rc = SQLITE_BUSY;
222606 ** fails with an SQLITE_BUSY error. This is to stop RBU connections
222942 rc = SQLITE_BUSY;
223059 if( ofst==WAL_LOCK_CKPT && n==1 ) rc = SQLITE_BUSY;