Lines Matching defs:SQLITE_BUSY
158 ** before this routine is called. Otherwise, SQLITE_BUSY is returned and the
243 #define SQLITE_BUSY 5 /* The database file is locked */
443 ** CAPI3REF: Register A Callback To Handle SQLITE_BUSY Errors
448 ** If the busy callback is NULL, then [SQLITE_BUSY]
458 ** access the database and [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED] is returned.
465 ** a deadlock, it will return [SQLITE_BUSY] instead.
473 ** SQLite returns [SQLITE_BUSY] for the first process, hoping that this
479 ** The [SQLITE_BUSY] error is converted to [SQLITE_IOERR_BLOCKED] when
487 ** code is promoted from the relatively benign [SQLITE_BUSY] to
515 ** causes [sqlite3_step()] to return [SQLITE_BUSY] or [SQLITE_IOERR_BLOCKED].
1317 ** In the lagacy interface, the return value will be either [SQLITE_BUSY],
1323 ** [SQLITE_BUSY] means that the database engine was unable to acquire the
1360 ** [SQLITE_ERROR], following any error other than [SQLITE_BUSY]
1380 ** After [sqlite3_step()] has returned an [SQLITE_DONE], [SQLITE_BUSY], or
