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;
24217 ** a normal expected return code of SQLITE_BUSY or SQLITE_OK
24219 #define IS_LOCK_ERROR(x) ((x != SQLITE_OK) && (x != SQLITE_BUSY))
24992 ** intended to translate a variety of "try again" errors into SQLITE_BUSY
25024 return SQLITE_BUSY;
25032 return SQLITE_BUSY;
25818 rc = SQLITE_BUSY;
25852 if( rc!=SQLITE_BUSY ){
25887 if( rc!=SQLITE_BUSY ){
25899 rc = SQLITE_BUSY;
25920 if( rc!=SQLITE_BUSY ){
26086 ** SQLITE_BUSY would confuse the upper layer (in practice it causes
26391 rc = SQLITE_BUSY;
26622 rc = SQLITE_BUSY;
26784 rc = SQLITE_BUSY;
26896 ** Return SQLITE_OK on success, SQLITE_BUSY on failure.
26924 rc = SQLITE_BUSY;
27055 rc = SQLITE_BUSY;
27129 rc = SQLITE_BUSY;
28361 rc = (rc!=(-1)) ? SQLITE_OK : SQLITE_BUSY;
28821 ** SQLITE_BUSY.
28825 rc = SQLITE_BUSY;
28846 ** lock. If any do, return SQLITE_BUSY right away.
28850 rc = SQLITE_BUSY;
30587 ** will fail and SQLITE_BUSY is returned.
30789 return SQLITE_BUSY;
30952 if( rc==SQLITE_BUSY ){
30974 return SQLITE_BUSY;
30987 return SQLITE_BUSY;
30991 return SQLITE_BUSY;
31008 } while( rc==SQLITE_BUSY && nTries<3 );
31102 rc = SQLITE_BUSY;
31122 rc = SQLITE_BUSY;
31190 rc=SQLITE_CANTOPEN_BKPT; /* SQLITE_BUSY? proxyTakeConch called
31312 return SQLITE_BUSY;
31379 return SQLITE_BUSY;
33175 ** the sqlite3_memory_used() function does not return zero, SQLITE_BUSY will
33210 rc = SQLITE_BUSY;
35015 rc = SQLITE_BUSY;
35408 rc = SQLITE_BUSY;
35680 ** SQLITE_BUSY.
35684 rc = SQLITE_BUSY;
35705 ** lock. If any do, return SQLITE_BUSY right away.
35709 rc = SQLITE_BUSY;
38218 if( rc!=SQLITE_OK && rc!=SQLITE_BUSY ){
40612 ** If the VFS xLock() or xUnlock() returns an error other than SQLITE_BUSY
43787 ** SQLITE_BUSY when trying to upgrade from no-lock to a SHARED lock,
43801 ** retried. If it returns zero, then the SQLITE_BUSY error is
44031 }while( rc==SQLITE_BUSY && pPager->xBusyHandler(pPager->pBusyHandlerArg) );
44436 ** SQLITE_BUSY is returned and no data is written to the database file.
44456 ** be obtained, SQLITE_BUSY is returned.
46290 ** Otherwise, either SQLITE_BUSY or an SQLITE_IOERR_XXX error code is
47422 ** error (SQLITE_BUSY) is returned and the log connection is not closed.
48262 VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && rc!=SQLITE_BUSY); )
48278 VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && rc!=SQLITE_BUSY); )
48538 ** the necessary locks, this routine returns SQLITE_BUSY.
49094 }while( xBusy && rc==SQLITE_BUSY && xBusy(pBusyArg) );
49186 }else if( rc==SQLITE_BUSY ){
49252 if( rc==SQLITE_BUSY ){
49266 rc = SQLITE_BUSY;
49512 ** I/O error or an SQLITE_BUSY because another process is running
49594 if( rc==SQLITE_BUSY ){
49604 /* This branch is taken when the xShmMap() method returns SQLITE_BUSY.
49607 ** modules may return SQLITE_BUSY due to a race condition in the
49615 }else if( rc==SQLITE_BUSY ){
49651 }else if( rc!=SQLITE_BUSY ){
49683 }else if( rc!=SQLITE_BUSY ){
49689 assert( rc==SQLITE_BUSY || (pWal->readOnly & WAL_SHM_RDONLY)!=0 );
49690 return rc==SQLITE_BUSY ? WAL_RETRY : SQLITE_READONLY_CANTLOCK;
49695 return rc==SQLITE_BUSY ? WAL_RETRY : rc;
49752 testcase( (rc&0xff)==SQLITE_BUSY );
49915 ** returns SQLITE_BUSY in that case and no write transaction is started.
49931 ** SQLITE_BUSY if unable.
50105 }else if( rc!=SQLITE_BUSY ){
50116 assert( (rc&0xff)!=SQLITE_BUSY ); /* BUSY not possible when useWal==1 */
50411 /* Usually this is SQLITE_BUSY meaning that another thread or process
50425 ** other error occurs, this function will return SQLITE_BUSY to the caller.
50431 }else if( rc==SQLITE_BUSY ){
50454 if( rc==SQLITE_OK || rc==SQLITE_BUSY ){
50475 return (rc==SQLITE_OK && eMode!=eMode2 ? SQLITE_BUSY : rc);
53932 ** SQLITE_BUSY is returned if the database is locked. SQLITE_NOMEM
54208 ** invoke the busy handler - just return SQLITE_BUSY. SQLITE_BUSY is
54215 ** no progress. By returning SQLITE_BUSY and not invoking the busy callback
54299 }while( (rc&0xFF)==SQLITE_BUSY && pBt->inTransaction==TRANS_NONE &&
60269 ** are considered fatal except for SQLITE_BUSY and SQLITE_LOCKED.
60272 return (rc!=SQLITE_OK && rc!=SQLITE_BUSY && ALWAYS(rc!=SQLITE_LOCKED));
60422 ** SQLITE_BUSY immediately.
60425 rc = SQLITE_BUSY;
60733 assert( rc!=SQLITE_BUSY && rc!=SQLITE_LOCKED );
63530 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY || p->rc==SQLITE_NOMEM );
64316 assert( rc!=SQLITE_BUSY );
64490 ** lock contention, return SQLITE_BUSY. If SQLITE_BUSY is returned, it
64594 if( rc==SQLITE_BUSY && p->readOnly ){
64596 return SQLITE_BUSY;
64682 return (p->rc==SQLITE_BUSY ? SQLITE_BUSY : SQLITE_OK);
66638 ** or SQLITE_BUSY error.
66641 if( p->rc==SQLITE_BUSY || p->rc==SQLITE_LOCKED ){
66729 || rc==SQLITE_BUSY || rc==SQLITE_MISUSE
68524 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY );
68931 assert( rc==SQLITE_BUSY || rc==SQLITE_OK || rc==SQLITE_ERROR );
68932 if( rc==SQLITE_BUSY ){
68933 p->rc = rc = SQLITE_BUSY;
70795 rc = SQLITE_BUSY;
70854 rc = SQLITE_BUSY;
70867 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
70870 p->rc = rc = SQLITE_BUSY;
70960 rc = SQLITE_BUSY;
70969 rc = SQLITE_BUSY;
70979 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
70982 p->rc = rc = SQLITE_BUSY;
71056 if( rc==SQLITE_BUSY ){
71058 p->rc = rc = SQLITE_BUSY;
71210 ** SQLITE_BUSY error code.
73733 ** SQLITE_BUSY or not, respectively. Write the number of pages in the
73752 if( rc==SQLITE_BUSY ){
122692 ** If lookaside is already active, return SQLITE_BUSY.
122703 return SQLITE_BUSY;
123014 ** SQLITE_BUSY if the connection can not be closed immediately.
123017 sqlite3Error(db, SQLITE_BUSY, "unable to close due to unfinalized "
123020 return SQLITE_BUSY;
123039 ** connection. The sqlite3_close() version returns SQLITE_BUSY and
123235 case SQLITE_BUSY: zName = "SQLITE_BUSY"; break;
123339 /* SQLITE_BUSY */ "database is locked",
123429 ** returns 0, the operation aborts with an SQLITE_BUSY error.
123573 ** and there are active VMs, then return SQLITE_BUSY. If a function
123580 sqlite3Error(db, SQLITE_BUSY,
123583 return SQLITE_BUSY;
123962 int bBusy = 0; /* True if SQLITE_BUSY has been encountered */
123973 if( rc==SQLITE_BUSY ){
123980 return (rc==SQLITE_OK && bBusy) ? SQLITE_BUSY : rc;
124188 sqlite3Error(db, SQLITE_BUSY,
124190 return SQLITE_BUSY;
