Lines Matching defs:SQLITE_BUSY
393 ** will leave the database connection open and return [SQLITE_BUSY].
519 #define SQLITE_BUSY 5 /* The database file is locked */
590 #define SQLITE_BUSY_RECOVERY (SQLITE_BUSY | (1<<8))
591 #define SQLITE_BUSY_SNAPSHOT (SQLITE_BUSY | (2<<8))
1900 ** [SQLITE_BUSY].)^</dd>
2145 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2155 ** ^If the busy callback is NULL, then [SQLITE_BUSY]
2164 ** access the database and [SQLITE_BUSY] is returned
2171 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2181 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2211 ** [SQLITE_BUSY].
3748 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
3753 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
3800 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
4908 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
6019 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
6031 ** will always return SQLITE_BUSY. The SQLite core only ever uses
6912 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
6928 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
6976 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
7343 ** lock cannot be obtained and SQLITE_BUSY is returned. Even if there is a
7355 ** without blocking any further. SQLITE_BUSY is returned in this case.
7360 ** an SQLITE_BUSY error is encountered when processing one or more of the
7362 ** attached databases and SQLITE_BUSY is returned to the caller. If any other
7365 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached
18487 ** thread holds the mutex and it cannot be obtained, return SQLITE_BUSY.
18671 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
18939 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
19014 rc = SQLITE_BUSY;
19027 rc = SQLITE_BUSY;
19619 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
19653 int rc = SQLITE_BUSY;
24224 ** a normal expected return code of SQLITE_BUSY or SQLITE_OK
24226 #define IS_LOCK_ERROR(x) ((x != SQLITE_OK) && (x != SQLITE_BUSY))
25010 ** intended to translate a variety of "try again" errors into SQLITE_BUSY
25042 return SQLITE_BUSY;
25050 return SQLITE_BUSY;
25836 rc = SQLITE_BUSY;
25870 if( rc!=SQLITE_BUSY ){
25905 if( rc!=SQLITE_BUSY ){
25917 rc = SQLITE_BUSY;
25938 if( rc!=SQLITE_BUSY ){
26104 ** SQLITE_BUSY would confuse the upper layer (in practice it causes
26409 rc = SQLITE_BUSY;
26640 rc = SQLITE_BUSY;
26802 rc = SQLITE_BUSY;
26914 ** Return SQLITE_OK on success, SQLITE_BUSY on failure.
26942 rc = SQLITE_BUSY;
27073 rc = SQLITE_BUSY;
27147 rc = SQLITE_BUSY;
28381 rc = (rc!=(-1)) ? SQLITE_OK : SQLITE_BUSY;
28841 ** SQLITE_BUSY.
28845 rc = SQLITE_BUSY;
28866 ** lock. If any do, return SQLITE_BUSY right away.
28870 rc = SQLITE_BUSY;
30607 ** will fail and SQLITE_BUSY is returned.
30809 return SQLITE_BUSY;
30972 if( rc==SQLITE_BUSY ){
30994 return SQLITE_BUSY;
31007 return SQLITE_BUSY;
31011 return SQLITE_BUSY;
31028 } while( rc==SQLITE_BUSY && nTries<3 );
31122 rc = SQLITE_BUSY;
31142 rc = SQLITE_BUSY;
31210 rc=SQLITE_CANTOPEN_BKPT; /* SQLITE_BUSY? proxyTakeConch called
31332 return SQLITE_BUSY;
31399 return SQLITE_BUSY;
33195 ** the sqlite3_memory_used() function does not return zero, SQLITE_BUSY will
33230 rc = SQLITE_BUSY;
35035 rc = SQLITE_BUSY;
35428 SQLITE_BUSY;
35700 ** SQLITE_BUSY.
35704 rc = SQLITE_BUSY;
35725 ** lock. If any do, return SQLITE_BUSY right away.
35729 rc = SQLITE_BUSY;
38238 if( rc!=SQLITE_OK && rc!=SQLITE_BUSY ){
40632 ** If the VFS xLock() or xUnlock() returns an error other than SQLITE_BUSY
43807 ** SQLITE_BUSY when trying to upgrade from no-lock to a SHARED lock,
43821 ** retried. If it returns zero, then the SQLITE_BUSY error is
44051 }while( rc==SQLITE_BUSY && pPager->xBusyHandler(pPager->pBusyHandlerArg) );
44456 ** SQLITE_BUSY is returned and no data is written to the database file.
44476 ** be obtained, SQLITE_BUSY is returned.
46310 ** Otherwise, either SQLITE_BUSY or an SQLITE_IOERR_XXX error code is
47442 ** error (SQLITE_BUSY) is returned and the log connection is not closed.
48282 VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && rc!=SQLITE_BUSY); )
48298 VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && rc!=SQLITE_BUSY); )
48558 ** the necessary locks, this routine returns SQLITE_BUSY.
49114 }while( xBusy && rc==SQLITE_BUSY && xBusy(pBusyArg) );
49206 }else if( rc==SQLITE_BUSY ){
49272 if( rc==SQLITE_BUSY ){
49286 rc = SQLITE_BUSY;
49532 ** I/O error or an SQLITE_BUSY because another process is running
49614 if( rc==SQLITE_BUSY ){
49624 /* This branch is taken when the xShmMap() method returns SQLITE_BUSY.
49627 ** modules may return SQLITE_BUSY due to a race condition in the
49635 }else if( rc==SQLITE_BUSY ){
49671 }else if( rc!=SQLITE_BUSY ){
49703 }else if( rc!=SQLITE_BUSY ){
49709 assert( rc==SQLITE_BUSY || (pWal->readOnly & WAL_SHM_RDONLY)!=0 );
49710 return rc==SQLITE_BUSY ? WAL_RETRY : SQLITE_READONLY_CANTLOCK;
49715 return rc==SQLITE_BUSY ? WAL_RETRY : rc;
49772 testcase( (rc&0xff)==SQLITE_BUSY );
49935 ** returns SQLITE_BUSY in that case and no write transaction is started.
49951 ** SQLITE_BUSY if unable.
50125 }else if( rc!=SQLITE_BUSY ){
50136 assert( (rc&0xff)!=SQLITE_BUSY ); /* BUSY not possible when useWal==1 */
50431 /* Usually this is SQLITE_BUSY meaning that another thread or process
50445 ** other error occurs, this function will return SQLITE_BUSY to the caller.
50451 }else if( rc==SQLITE_BUSY ){
50474 if( rc==SQLITE_OK || rc==SQLITE_BUSY ){
50495 return (rc==SQLITE_OK && eMode!=eMode2 ? SQLITE_BUSY : rc);
53952 ** SQLITE_BUSY is returned if the database is locked. SQLITE_NOMEM
54228 ** invoke the busy handler - just return SQLITE_BUSY. SQLITE_BUSY is
54235 ** no progress. By returning SQLITE_BUSY and not invoking the busy callback
54319 }while( (rc&0xFF)==SQLITE_BUSY && pBt->inTransaction==TRANS_NONE &&
60289 ** are considered fatal except for SQLITE_BUSY and SQLITE_LOCKED.
60292 return (rc!=SQLITE_OK && rc!=SQLITE_BUSY && ALWAYS(rc!=SQLITE_LOCKED));
60442 ** SQLITE_BUSY immediately.
60445 rc = SQLITE_BUSY;
60753 assert( rc!=SQLITE_BUSY && rc!=SQLITE_LOCKED );
63550 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY || p->rc==SQLITE_NOMEM );
64336 assert( rc!=SQLITE_BUSY );
64510 ** lock contention, return SQLITE_BUSY. If SQLITE_BUSY is returned, it
64614 if( rc==SQLITE_BUSY && p->readOnly ){
64616 return SQLITE_BUSY;
64702 return (p->rc==SQLITE_BUSY ? SQLITE_BUSY : SQLITE_OK);
66658 ** or SQLITE_BUSY error.
66661 if( p->rc==SQLITE_BUSY || p->rc==SQLITE_LOCKED ){
66749 || rc==SQLITE_BUSY || rc==SQLITE_MISUSE
68544 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY );
68951 assert( rc==SQLITE_BUSY || rc==SQLITE_OK || rc==SQLITE_ERROR );
68952 if( rc==SQLITE_BUSY ){
68953 p->rc = rc = SQLITE_BUSY;
70815 rc = SQLITE_BUSY;
70874 rc = SQLITE_BUSY;
70887 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
70890 p->rc = rc = SQLITE_BUSY;
70980 rc = SQLITE_BUSY;
70989 rc = SQLITE_BUSY;
70999 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
71002 p->rc = rc = SQLITE_BUSY;
71076 if( rc==SQLITE_BUSY ){
71078 p->rc = rc = SQLITE_BUSY;
71230 ** SQLITE_BUSY error code.
73753 ** SQLITE_BUSY or not, respectively. Write the number of pages in the
73772 if( rc==SQLITE_BUSY ){
122712 ** If lookaside is already active, return SQLITE_BUSY.
122723 return SQLITE_BUSY;
123034 ** SQLITE_BUSY if the connection can not be closed immediately.
123037 sqlite3Error(db, SQLITE_BUSY, "unable to close due to unfinalized "
123040 return SQLITE_BUSY;
123059 ** connection. The sqlite3_close() version returns SQLITE_BUSY and
123255 case SQLITE_BUSY: zName = "SQLITE_BUSY"; break;
123359 /* SQLITE_BUSY */ "database is locked",
123449 ** returns 0, the operation aborts with an SQLITE_BUSY error.
123593 ** and there are active VMs, then return SQLITE_BUSY. If a function
123600 sqlite3Error(db, SQLITE_BUSY,
123603 return SQLITE_BUSY;
123982 int bBusy = 0; /* True if SQLITE_BUSY has been encountered */
123993 if( rc==SQLITE_BUSY ){
124000 return (rc==SQLITE_OK && bBusy) ? SQLITE_BUSY : rc;
124208 sqlite3Error(db, SQLITE_BUSY,
124210 return SQLITE_BUSY;
