contrib/sqlite3/sqlite3.c

849 ** will leave the database connection open and return [SQLITE_BUSY].
977 #define SQLITE_BUSY         5   /* The database file is locked */
1053 #define SQLITE_BUSY_RECOVERY           (SQLITE_BUSY   |  (1<<8))
2305 ** [SQLITE_BUSY].)^</dd>
2548 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2554 ** ^If the busy callback is NULL, then [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED]
2563 ** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
2569 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2578 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2584 ** ^The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED]
2592 ** code is promoted from the relatively benign [SQLITE_BUSY] to
2621 ** [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
4128 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
4133 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
4180 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE].  You must call
5239 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
6316 ** SQLITE_BUSY.  ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
6328 ** will always return SQLITE_BUSY.  The SQLite core only ever uses
7185 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
7201 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
7249 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
7606 ** lock cannot be obtained and SQLITE_BUSY is returned. Even if there is a
7618 ** without blocking any further. SQLITE_BUSY is returned in this case.
7623 ** an SQLITE_BUSY error is encountered when processing one or more of the
7625 ** attached databases and SQLITE_BUSY is returned to the caller. If any other
7628 ** (SQLITE_BUSY or otherwise) is encountered while processing the attached
17823 ** thread holds the mutex and it cannot be obtained, return SQLITE_BUSY.
18007 ** SQLITE_BUSY.  The sqlite3_mutex_try() interface returns SQLITE_OK
18269 ** SQLITE_BUSY.  The sqlite3_mutex_try() interface returns SQLITE_OK
18344       rc = SQLITE_BUSY;
18357     rc = SQLITE_BUSY;
18664 ** SQLITE_BUSY.  The sqlite3_mutex_try() interface returns SQLITE_OK
18690   int rc = SQLITE_BUSY;
23073 ** a normal expected return code of SQLITE_BUSY or SQLITE_OK
23075 #define IS_LOCK_ERROR(x)  ((x != SQLITE_OK) && (x != SQLITE_BUSY))
23811 ** intended to translate a variety of "try again" errors into SQLITE_BUSY
23843     return SQLITE_BUSY;
23851       return SQLITE_BUSY;
24637     rc = SQLITE_BUSY;
24671       if( rc!=SQLITE_BUSY ){
24706       if( rc!=SQLITE_BUSY ){
24718     rc = SQLITE_BUSY;
24739       if( rc!=SQLITE_BUSY ){
24905           ** SQLITE_BUSY would confuse the upper layer (in practice it causes
25197       rc = SQLITE_BUSY;
25428     rc = SQLITE_BUSY;
25592     rc = SQLITE_BUSY;
25704 ** Return SQLITE_OK on success, SQLITE_BUSY on failure.
25732     rc = SQLITE_BUSY;
25863     rc = SQLITE_BUSY;
25937     rc = SQLITE_BUSY;
27136     rc = (rc!=(-1)) ? SQLITE_OK : SQLITE_BUSY;
27569     ** SQLITE_BUSY.
27573         rc = SQLITE_BUSY;
27594     ** lock.  If any do, return SQLITE_BUSY right away.
27598         rc = SQLITE_BUSY;
29320 ** will fail and SQLITE_BUSY is returned.
29522       return SQLITE_BUSY;
29685     if( rc==SQLITE_BUSY ){
29707         return SQLITE_BUSY;
29720             return SQLITE_BUSY;
29724           return SQLITE_BUSY;
29741   } while( rc==SQLITE_BUSY && nTries<3 );
29835         rc = SQLITE_BUSY;
29855           rc = SQLITE_BUSY;
29923           rc=SQLITE_CANTOPEN_BKPT; /* SQLITE_BUSY? proxyTakeConch called
30045     return SQLITE_BUSY;
30112     return SQLITE_BUSY;
33436     rc = SQLITE_BUSY;
33807     rc = SQLITE_BUSY;
34078     ** SQLITE_BUSY.
34082         rc = SQLITE_BUSY;
34103     ** lock.  If any do, return SQLITE_BUSY right away.
34107         rc = SQLITE_BUSY;
36315       if( rc!=SQLITE_OK && rc!=SQLITE_BUSY ){
38698 ** If the VFS xLock() or xUnlock() returns an error other than SQLITE_BUSY
41856 ** SQLITE_BUSY when trying to upgrade from no-lock to a SHARED lock,
41870 ** retried. If it returns zero, then the SQLITE_BUSY error is
42100   }while( rc==SQLITE_BUSY && pPager->xBusyHandler(pPager->pBusyHandlerArg) );
42505 ** SQLITE_BUSY is returned and no data is written to the database file.
42525 ** be obtained, SQLITE_BUSY is returned.
44313 ** Otherwise, either SQLITE_BUSY or an SQLITE_IOERR_XXX error code is
45423 ** error (SQLITE_BUSY) is returned and the log connection is not closed.
46278   VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && rc!=SQLITE_BUSY); )
46294   VVA_ONLY( pWal->lockError = (u8)(rc!=SQLITE_OK && rc!=SQLITE_BUSY); )
46554 ** the necessary locks, this routine returns SQLITE_BUSY.
47110   }while( xBusy && rc==SQLITE_BUSY && xBusy(pBusyArg) );
47202       }else if( rc==SQLITE_BUSY ){
47268   if( rc==SQLITE_BUSY ){
47282       rc = SQLITE_BUSY;
47528 ** I/O error or an SQLITE_BUSY because another process is running
47610     if( rc==SQLITE_BUSY ){
47620         /* This branch is taken when the xShmMap() method returns SQLITE_BUSY.
47623         ** modules may return SQLITE_BUSY due to a race condition in the
47631       }else if( rc==SQLITE_BUSY ){
47667     }else if( rc!=SQLITE_BUSY ){
47699         }else if( rc!=SQLITE_BUSY ){
47705       assert( rc==SQLITE_BUSY || (pWal->readOnly & WAL_SHM_RDONLY)!=0 );
47706       return rc==SQLITE_BUSY ? WAL_RETRY : SQLITE_READONLY_CANTLOCK;
47711       return rc==SQLITE_BUSY ? WAL_RETRY : rc;
47768   testcase( (rc&0xff)==SQLITE_BUSY );
47931 ** returns SQLITE_BUSY in that case and no write transaction is started.
47947   ** SQLITE_BUSY if unable.
47962     rc = SQLITE_BUSY;
48121       }else if( rc!=SQLITE_BUSY ){
48132     assert( (rc&0xff)!=SQLITE_BUSY ); /* BUSY not possible when useWal==1 */
48427     /* Usually this is SQLITE_BUSY meaning that another thread or process
48441   ** other error occurs, this function will return SQLITE_BUSY to the caller.
48447     }else if( rc==SQLITE_BUSY ){
48470     if( rc==SQLITE_OK || rc==SQLITE_BUSY ){
48491   return (rc==SQLITE_OK && eMode!=eMode2 ? SQLITE_BUSY : rc);
51916 ** SQLITE_BUSY is returned if the database is locked.  SQLITE_NOMEM
52191 ** invoke the busy handler - just return SQLITE_BUSY.  SQLITE_BUSY is
52198 ** no progress.  By returning SQLITE_BUSY and not invoking the busy callback
52282   }while( (rc&0xFF)==SQLITE_BUSY && pBt->inTransaction==TRANS_NONE &&
58236 ** are considered fatal except for SQLITE_BUSY and SQLITE_LOCKED.
58239   return (rc!=SQLITE_OK && rc!=SQLITE_BUSY && ALWAYS(rc!=SQLITE_LOCKED));
58389     ** SQLITE_BUSY immediately.
58392       rc = SQLITE_BUSY;
58700       assert( rc!=SQLITE_BUSY && rc!=SQLITE_LOCKED );
61083   assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY || p->rc==SQLITE_NOMEM );
61871     assert( rc!=SQLITE_BUSY );
62039 ** lock contention, return SQLITE_BUSY.  If SQLITE_BUSY is returned, it
62143         if( rc==SQLITE_BUSY && p->readOnly ){
62145           return SQLITE_BUSY;
62228   return (p->rc==SQLITE_BUSY ? SQLITE_BUSY : SQLITE_OK);
63555     ** or SQLITE_BUSY error.
63558     if( p->rc==SQLITE_BUSY || p->rc==SQLITE_LOCKED ){
63643        || rc==SQLITE_BUSY || rc==SQLITE_MISUSE
65415 ** return SQLITE_BUSY.
65897   assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY );
66183   assert( rc==SQLITE_BUSY || rc==SQLITE_OK || rc==SQLITE_ERROR );
66184   if( rc==SQLITE_BUSY ){
66185     p->rc = rc = SQLITE_BUSY;
68049       rc = SQLITE_BUSY;
68107       rc = SQLITE_BUSY;
68120         if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
68123           p->rc = rc = SQLITE_BUSY;
68213     rc = SQLITE_BUSY;
68222     rc = SQLITE_BUSY;
68232       if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
68235         p->rc = rc = SQLITE_BUSY;
68300     if( rc==SQLITE_BUSY ){
68302       p->rc = rc = SQLITE_BUSY;
68486 ** SQLITE_BUSY error code.
70913 ** SQLITE_BUSY or not, respectively.  Write the number of pages in the
70933   if( rc==SQLITE_BUSY ){
115305 ** If lookaside is already active, return SQLITE_BUSY.
115316     return SQLITE_BUSY;
115623   ** SQLITE_BUSY if the connection can not be closed immediately.
115626     sqlite3Error(db, SQLITE_BUSY, "unable to close due to unfinalized "
115629     return SQLITE_BUSY;
115648 ** connection. The sqlite3_close() version returns SQLITE_BUSY and
115846       case SQLITE_BUSY:               zName = "SQLITE_BUSY";              break;
115944     /* SQLITE_BUSY        */ "database is locked",
116034 ** returns 0, the operation aborts with an SQLITE_BUSY error.
116173   ** and there are active VMs, then return SQLITE_BUSY. If a function
116180       sqlite3Error(db, SQLITE_BUSY,
116183       return SQLITE_BUSY;
116561   int bBusy = 0;                  /* True if SQLITE_BUSY has been encountered */
116572       if( rc==SQLITE_BUSY ){
116579   return (rc==SQLITE_OK && bBusy) ? SQLITE_BUSY : rc;
116761       sqlite3Error(db, SQLITE_BUSY,
116763       return SQLITE_BUSY;