Home
last modified time | relevance | path

Searched refs:pending (Results 1 – 20 of 20) sorted by relevance

/sqlite-3.40.0/test/
H A Dfts3cov.test112 # terms in the pending-hash table. Specifically, while creating doclist
144 # If too much data accumulates in the pending-terms hash table, it is
180 # 1. When flushing the pending-terms table.
192 # Test when flushing pending-terms table.
277 # pending-terms table must be flushed each time a document with a docid
281 # pending-terms table is flushed for this reason as part of a DELETE
325 # the pending-terms table is non-empty. This case involves some extra
327 # also from the pending-terms table.
H A Dsavepoint7.test13 # pending query aborts. See ticket [27ca74af3c083f787a1c44b11fbb7c53bdbbcf1e].
19 # The RELEASE of an inner savepoint should not effect pending queries.
H A Dbackup.test29 # backup-3.*: Verify that the locking-page (pending byte page) is handled.
251 # the locks are applied to). These tests assume that the pending
267 # * Source database includes pending-byte page.
268 # * Source database does not include pending-byte page.
270 # * Target database includes pending-byte page.
271 # * Target database does not include pending-byte page.
H A Dfts3auto.test586 foreach {tn create pending} {
600 if {$pending} {execsql BEGIN}
633 if {$pending} {execsql COMMIT}
637 foreach {tn pending create} {
649 if {$pending} { execsql BEGIN }
H A Dtkt1667.test30 # Set the pending byte offset such that the page it is on is
H A Dtrans3.test14 # statements are still pending.
H A Dtkt3093.test43 # Make sure that clearing a lock allows a pending request for
H A Dfts4unicode.test102 Pending statements no longer block ROLLBACK. Instead, the pending statement
156 ...[ROLLBACK]. Instead, the pending statement
160 ...[ROLLBACK]. Instead, the pending statement
H A Dattach2.test299 lock_status 4.10.2 db2 {main pending temp closed file2 reserved}
308 lock_status 4.11.2 db2 {main pending temp closed file2 reserved}
H A Dnotify1.test61 # a NULL xNotify argument) cancels a pending notify callback.
441 # Test cases notify1-9.* test the shared-cache 'pending-lock' feature.
H A Drollback.test13 # caused by an ON CONFLICT ROLLBACK clause aborts any other pending
H A Dserver1.test117 # will leave the lock pending.
H A De_walckpt.test529 # while it is pending, but new database readers are allowed to continue
533 # blocks new database writer attempts while it is pending, but does not
H A Dbackup_ioerr.test80 # pending-byte (locking) page.
H A Dcorrupt2.test534 # pending-byte page (AKA the locking page). This test verifies that if
H A Dpager1.test203 } {main pending temp closed}
/sqlite-3.40.0/ext/async/
H A DREADME.txt77 thread, the queue of pending write operations will grow without bound.
80 pending writes and stop accepting new write requests when the queue of
81 pending writes grows too large.
/sqlite-3.40.0/ext/fts5/test/
H A Dfts5unicode2.test109 Pending statements no longer block ROLLBACK. Instead, the pending statement
163 Pending statements no longer block [ROLLBACK]. Instead, the pending
167 Pending statements no longer block [ROLLBACK]. Instead, the pending
/sqlite-3.40.0/src/
H A Dtest_osinst.c623 int pending = sqlite3_io_error_pending; in vfslog_flush() local
639 sqlite3_io_error_pending = pending; in vfslog_flush()
H A Dsqlite.h.in2640 ** ^This function causes any pending database operation to abort and
4963 ** are pending, then the results are undefined.
6419 ** pending.</dd>
9373 ** database file. ^This mode blocks new database writers while it is pending,
9383 ** database writer attempts while it is pending, but does not impede readers.