• Home
  • History
  • Annotate
  • Raw
  • Download
  • only in /netgear-R7000-V1.0.7.12_1.2.5/ap/gpl/iserver/sqlite-3.6.22/

Lines Matching defs:SQLITE_BUSY

778 ** SQLITE_BUSY.
886 #define SQLITE_BUSY 5 /* The database file is locked */
2036 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2042 ** ^If the busy callback is NULL, then [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED]
2051 ** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
2057 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2066 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2072 ** ^The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED]
2080 ** code is promoted from the relatively benign [SQLITE_BUSY] to
2109 ** [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
3341 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
3346 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
3381 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
4275 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
5223 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
5235 ** will always return SQLITE_BUSY. The SQLite core only ever uses
5924 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
5936 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
5984 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
14473 ** thread holds the mutex and it cannot be obtained, return SQLITE_BUSY.
14649 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
14894 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
14925 rc = SQLITE_BUSY;
15154 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
15226 rc = SQLITE_BUSY;
15237 rc = SQLITE_BUSY;
15507 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
15521 int rc = SQLITE_BUSY;
20550 rc = SQLITE_BUSY;
21428 ** a normal expected return code of SQLITE_BUSY or SQLITE_OK
21430 #define IS_LOCK_ERROR(x) ((x != SQLITE_OK) && (x != SQLITE_BUSY))
21868 ** intended to translate a variety of "try again" errors into SQLITE_BUSY
21887 return SQLITE_BUSY;
21895 return SQLITE_BUSY;
22819 rc = SQLITE_BUSY;
22900 rc = SQLITE_BUSY;
23358 rc = SQLITE_BUSY;
23576 rc = SQLITE_BUSY;
23619 r = SQLITE_BUSY;
23747 rc = SQLITE_BUSY;
23860 ** Return SQLITE_OK on success, SQLITE_BUSY on failure.
23888 rc = SQLITE_BUSY;
25939 ** will fail and SQLITE_BUSY is returned.
26370 rc=SQLITE_CANTOPEN; /* SQLITE_BUSY? proxyTakeConch called
26471 return SQLITE_BUSY;
26538 return SQLITE_BUSY;
28136 rc = SQLITE_BUSY;
29694 if( rc!=SQLITE_OK && rc!=SQLITE_BUSY ){
31442 ** fails, then SQLITE_BUSY may be returned to the user and the user
33486 ** SQLITE_BUSY when trying to upgrade from no-lock to a SHARED lock,
33500 ** retried. If it returns zero, then the SQLITE_BUSY error is
33772 }while( rc==SQLITE_BUSY && pPager->xBusyHandler(pPager->pBusyHandlerArg) );
34036 ** SQLITE_BUSY is returned and no data is written to the database file.
34056 ** be obtained, SQLITE_BUSY is returned.
39783 ** SQLITE_BUSY is returned if the database is locked. SQLITE_NOMEM
39975 ** invoke the busy handler - just return SQLITE_BUSY. SQLITE_BUSY is
39982 ** no progress. By returning SQLITE_BUSY and not invoking the busy callback
40061 }while( rc==SQLITE_BUSY && pBt->inTransaction==TRANS_NONE &&
45607 ** are considered fatal except for SQLITE_BUSY and SQLITE_LOCKED.
45610 return (rc!=SQLITE_OK && rc!=SQLITE_BUSY && ALWAYS(rc!=SQLITE_LOCKED));
45722 ** SQLITE_BUSY immediately.
45725 rc = SQLITE_BUSY;
45973 assert( rc!=SQLITE_BUSY && rc!=SQLITE_LOCKED );
48210 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY || p->rc==SQLITE_NOMEM );
49155 ** lock contention, return SQLITE_BUSY. If SQLITE_BUSY is returned, it
49245 if( rc==SQLITE_BUSY ){
49247 return SQLITE_BUSY;
50640 || rc==SQLITE_BUSY || rc==SQLITE_MISUSE
52238 ** return SQLITE_BUSY.
52689 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY );
52974 assert( rc==SQLITE_BUSY || rc==SQLITE_OK || rc==SQLITE_ERROR );
52975 if( rc==SQLITE_BUSY ){
52976 p->rc = rc = SQLITE_BUSY;
54684 rc = SQLITE_BUSY;
54735 rc = SQLITE_BUSY;
54748 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
54751 p->rc = rc = SQLITE_BUSY;
54829 rc = SQLITE_BUSY;
54836 rc = SQLITE_BUSY;
54846 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
54849 p->rc = rc = SQLITE_BUSY;
54914 if( rc==SQLITE_BUSY ){
54916 p->rc = rc = SQLITE_BUSY;
55089 ** SQLITE_BUSY error code.
95604 ** If lookaside is already active, return SQLITE_BUSY.
95615 return SQLITE_BUSY;
95819 /* If there are any outstanding VMs, return SQLITE_BUSY. */
95821 sqlite3Error(db, SQLITE_BUSY,
95824 return SQLITE_BUSY;
95831 sqlite3Error(db, SQLITE_BUSY,
95834 return SQLITE_BUSY;
95964 /* SQLITE_BUSY */ "database is locked",
96045 ** returns 0, the operation aborts with an SQLITE_BUSY error.
96182 ** and there are active VMs, then return SQLITE_BUSY. If a function
96189 sqlite3Error(db, SQLITE_BUSY,
96192 return SQLITE_BUSY;
96608 sqlite3Error(db, SQLITE_BUSY,
96610 return SQLITE_BUSY;