• Home
  • History
  • Annotate
  • Raw
  • Download
  • only in /netgear-WNDR4500-V1.0.1.40_1.0.68/ap/gpl/minidlna/sqlite-3.6.22/

Lines Matching refs:SQLITE_BUSY

775 ** SQLITE_BUSY.
883 #define SQLITE_BUSY 5 /* The database file is locked */
2033 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
2039 ** ^If the busy callback is NULL, then [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED]
2048 ** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
2054 ** handler could result in a deadlock, it will go ahead and return [SQLITE_BUSY]
2063 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
2069 ** ^The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED]
2077 ** code is promoted from the relatively benign [SQLITE_BUSY] to
2106 ** [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
3338 ** ^In the legacy interface, the return value will be either [SQLITE_BUSY],
3343 ** ^[SQLITE_BUSY] means that the database engine was unable to acquire the
3378 ** error other than [SQLITE_BUSY] and [SQLITE_MISUSE]. You must call
4272 ** [SQLITE_NOMEM], [SQLITE_BUSY], and [SQLITE_INTERRUPT]) then the
5220 ** SQLITE_BUSY. ^The sqlite3_mutex_try() interface returns [SQLITE_OK]
5232 ** will always return SQLITE_BUSY. The SQLite core only ever uses
5921 ** [SQLITE_NOMEM], [SQLITE_BUSY], [SQLITE_LOCKED], or an
5933 ** [SQLITE_BUSY] is returned to the caller. ^In this case the call to
5981 ** ^A return of [SQLITE_BUSY] or [SQLITE_LOCKED] from sqlite3_backup_step()
14470 ** thread holds the mutex and it cannot be obtained, return SQLITE_BUSY.
14646 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
14891 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
14922 rc = SQLITE_BUSY;
15151 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
15223 rc = SQLITE_BUSY;
15234 rc = SQLITE_BUSY;
15504 ** SQLITE_BUSY. The sqlite3_mutex_try() interface returns SQLITE_OK
15518 int rc = SQLITE_BUSY;
20547 rc = SQLITE_BUSY;
21425 ** a normal expected return code of SQLITE_BUSY or SQLITE_OK
21427 #define IS_LOCK_ERROR(x) ((x != SQLITE_OK) && (x != SQLITE_BUSY))
21865 ** intended to translate a variety of "try again" errors into SQLITE_BUSY
21884 return SQLITE_BUSY;
21892 return SQLITE_BUSY;
22816 rc = SQLITE_BUSY;
22897 rc = SQLITE_BUSY;
23355 rc = SQLITE_BUSY;
23573 rc = SQLITE_BUSY;
23616 r = SQLITE_BUSY;
23744 rc = SQLITE_BUSY;
23857 ** Return SQLITE_OK on success, SQLITE_BUSY on failure.
23885 rc = SQLITE_BUSY;
25936 ** will fail and SQLITE_BUSY is returned.
26367 rc=SQLITE_CANTOPEN; /* SQLITE_BUSY? proxyTakeConch called
26468 return SQLITE_BUSY;
26535 return SQLITE_BUSY;
28133 rc = SQLITE_BUSY;
29691 if( rc!=SQLITE_OK && rc!=SQLITE_BUSY ){
31439 ** fails, then SQLITE_BUSY may be returned to the user and the user
33483 ** SQLITE_BUSY when trying to upgrade from no-lock to a SHARED lock,
33497 ** retried. If it returns zero, then the SQLITE_BUSY error is
33769 }while( rc==SQLITE_BUSY && pPager->xBusyHandler(pPager->pBusyHandlerArg) );
34033 ** SQLITE_BUSY is returned and no data is written to the database file.
34053 ** be obtained, SQLITE_BUSY is returned.
39780 ** SQLITE_BUSY is returned if the database is locked. SQLITE_NOMEM
39972 ** invoke the busy handler - just return SQLITE_BUSY. SQLITE_BUSY is
39979 ** no progress. By returning SQLITE_BUSY and not invoking the busy callback
40058 }while( rc==SQLITE_BUSY && pBt->inTransaction==TRANS_NONE &&
45604 ** are considered fatal except for SQLITE_BUSY and SQLITE_LOCKED.
45607 return (rc!=SQLITE_OK && rc!=SQLITE_BUSY && ALWAYS(rc!=SQLITE_LOCKED));
45719 ** SQLITE_BUSY immediately.
45722 rc = SQLITE_BUSY;
45970 assert( rc!=SQLITE_BUSY && rc!=SQLITE_LOCKED );
48207 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY || p->rc==SQLITE_NOMEM );
49152 ** lock contention, return SQLITE_BUSY. If SQLITE_BUSY is returned, it
49242 if( rc==SQLITE_BUSY ){
49244 return SQLITE_BUSY;
50637 || rc==SQLITE_BUSY || rc==SQLITE_MISUSE
52235 ** return SQLITE_BUSY.
52686 assert( p->rc==SQLITE_OK || p->rc==SQLITE_BUSY );
52971 assert( rc==SQLITE_BUSY || rc==SQLITE_OK || rc==SQLITE_ERROR );
52972 if( rc==SQLITE_BUSY ){
52973 p->rc = rc = SQLITE_BUSY;
54681 rc = SQLITE_BUSY;
54732 rc = SQLITE_BUSY;
54745 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
54748 p->rc = rc = SQLITE_BUSY;
54826 rc = SQLITE_BUSY;
54833 rc = SQLITE_BUSY;
54843 if( sqlite3VdbeHalt(p)==SQLITE_BUSY ){
54846 p->rc = rc = SQLITE_BUSY;
54911 if( rc==SQLITE_BUSY ){
54913 p->rc = rc = SQLITE_BUSY;
55086 ** SQLITE_BUSY error code.
95601 ** If lookaside is already active, return SQLITE_BUSY.
95612 return SQLITE_BUSY;
95816 /* If there are any outstanding VMs, return SQLITE_BUSY. */
95818 sqlite3Error(db, SQLITE_BUSY,
95821 return SQLITE_BUSY;
95828 sqlite3Error(db, SQLITE_BUSY,
95831 return SQLITE_BUSY;
95961 /* SQLITE_BUSY */ "database is locked",
96042 ** returns 0, the operation aborts with an SQLITE_BUSY error.
96179 ** and there are active VMs, then return SQLITE_BUSY. If a function
96186 sqlite3Error(db, SQLITE_BUSY,
96189 return SQLITE_BUSY;
96605 sqlite3Error(db, SQLITE_BUSY,
96607 return SQLITE_BUSY;