Lines Matching full:busy
913 ** to the connections busy-handler callback. The argument is of type (void **)
916 ** busy-handler, this function should be invoked with the second (void *) in
2109 ** KEYWORDS: {busy-handler callback} {busy handler}
2120 ** ^If the busy callback is NULL, then [SQLITE_BUSY]
2121 ** is returned immediately upon encountering the lock. ^If the busy callback
2124 ** ^The first argument to the busy handler is a copy of the void* pointer which
2126 ** the busy handler callback is the number of times that the busy handler has
2128 ** busy callback returns 0, then no additional attempts are made to
2134 ** The presence of a busy handler does not guarantee that it will be invoked
2135 ** when there is lock contention. ^If SQLite determines that invoking the busy
2138 ** busy handler.
2145 ** invoke the busy handlers, neither will make any progress. Therefore,
2150 ** ^The default busy callback is NULL.
2152 ** ^(There can only be a single busy handler defined for each
2153 ** [database connection]. Setting a new busy handler clears any
2156 ** busy handler and thus clear any previously set busy handler.
2158 ** The busy callback should not take any actions which modify the
2159 ** database connection that invoked the busy handler. In other words,
2160 ** the busy handler is not reentrant. Any such actions
2163 ** A busy handler must not close the database connection
2164 ** or [prepared statement] that invoked the busy handler.
2169 ** CAPI3REF: Set A Busy Timeout
2172 ** ^This routine sets a [sqlite3_busy_handler | busy handler] that sleeps
2180 ** turns off all busy handlers.
2182 ** ^(There can only be a single busy handler for a particular
2183 ** [database connection] at any given moment. If another busy handler
2185 ** this routine, that other busy handler is cleared.)^
7113 ** the [sqlite3_busy_handler | busy-handler function]
7115 ** busy-handler returns non-zero before the lock is available, then
7502 ** in the log were checkpointed. ^The [busy-handler callback]
7509 ** [sqlite3_busy_handler|busy-handler callback]) until there is no
7518 ** [busy-handler callback])
7543 ** busy-handler configured, it will not be invoked in this case.
7547 ** obtained immediately, and a busy-handler is configured, it is invoked and
7548 ** the writer lock retried until either the busy-handler returns 0 or the lock
7549 ** is successfully obtained. ^The busy-handler is also invoked while waiting for
7550 ** database readers as described above. ^If the busy-handler returns 0 before
