Searched refs:scenario (Results 1 – 13 of 13) sorted by relevance
54 proc scenario {id title pattern} { procedure66 scenario 0 {Default} {}67 scenario 1 {Debug} {71 scenario 2 {Everything} {79 scenario 3 {Customer-1} {94 scenario 4 {Small-Cache} {
12 # This file attempts to duplicate an error scenario seen on a
11 # This file implements tests for a strange scenario discovered by
101 # The following tests - thread1-2.* - test the following scenario:
55 # Potential corruption scenario 1. A second process opens the database 76 # Potential corruption scenario 2. The second process, operating in
66 # Test an unusual scenario:
301 # The following tests - incrblob2-6.* - test a specific scenario that might
324 # the index B-Tree. At one point this (obscure) scenario was causing
405 # call sync() in this scenario. So no further memory can be reclaimed.
412 # Ticket #350 describes a scenario where LEFT OUTER JOIN does not
629 # than that. In this scenario SQLite should delete the journal file
529 # Ticket #350 describes a scenario where LEFT OUTER JOIN does not
2741 ** Consider a scenario where one process is holding a read lock that9144 ** To avoid this scenario, the sqlite3_unlock_notify() performs deadlock