Home
last modified time | relevance | path

Searched refs:transaction (Results 1 – 25 of 183) sorted by relevance

12345678

/sqlite-3.40.0/test/
H A Dtclsqlite.test383 db transaction {}
403 db transaction {
405 db transaction {
413 db transaction {
423 db transaction {
437 db transaction {
447 db transaction {
472 db transaction {
496 db transaction {
498 db transaction {
[all …]
H A Dtkt2409.test24 # a db transaction but does not start a statement transaction.
25 # Verify that the transaction is automatically rolled back
34 # during a database COMMIT. Verify that the transaction is not
38 # within a transaction instead of just one.
43 # INSERT statement starts a statement transaction. Verify that
44 # SQLITE_BUSY is returned and the transaction is not rolled back.
109 # Check that the transaction was rolled back. Because the INSERT
111 # transaction, SQLite had no choice but to roll back the transaction.
177 # Check that the transaction was rolled back. Because the INSERT
179 # transaction, SQLite had no choice but to roll back the transaction.
H A Djrnlmode3.test28 # transaction, even if locking_mode=EXCLUSIVE is enabled. The behavior if
29 # journal_mode is changed after the first transaction is undefined and hence
73 # to any other, as long as we are not in a transaction. Verify
74 # that we cannot change journal_mode while a transaction is active.
103 # Start a transaction and try to change the journal mode within
104 # the transaction. This should fail.
115 # Rollback the transaction.
131 # Do a the transaction. Verify that the rollback occurred
H A Dshared.test82 # shared-11.*: Test transaction locking.
133 # Upgrade connection 1's transaction to a write transaction. Create
137 # has finished the transaction.
156 # Commit the connection 1 transaction.
188 # Turn db's transaction into a write-transaction. db3 should still be
195 # db2 transaction back and replace it with a new read transaction.
212 # Commit the open transaction on db. db2 still holds a read-transaction.
358 # Cleanup: commit the transaction opened by db2.
786 # Open a read-transaction with the first connection, a write-transaction
844 # Commit the external transaction.
[all …]
H A Dmalloc3.test31 # it is possible for a single DML statement in an implicit transaction
32 # to fail with SQLITE_NOMEM, but for the transaction to still end up
47 # database file and end the transaction, leaving whatever journal and
49 # (or any other) connection opens a read transaction, hot-journal rollback
103 # transaction rollback is required, all other vdbe's are aborted.
155 # below) figures out if a transaction has been automatically rolled back.
159 # If a transaction has been automatically rolled back, then the driver
169 # * If a PREP block starts a transaction, it must finish it.
170 # * A PREP block may not close a transaction it did not start.
192 # transaction only.
[all …]
H A Dnotify2.test34 # transaction consists of 3 operations. Each operation is either a read
37 # error is returned the current transaction is rolled back immediately.
41 # that sqlite3_blocking_step() resulted in higher transaction throughput.
108 # Each transaction does 3 operations. Each operation is either a read
131 # Execute the SQL transaction.
146 # Hit an SQLITE_LOCKED error. Rollback the current transaction.
156 # No error occurred. Check that any SELECT statements in the transaction
236 # for this type of test. The number of CPU cycles per transaction is
238 # number of SQLITE_BUSY or SQLITE_LOCKED errors that require the transaction
H A Dtkt35xx.test13 # When a transaction rolls back, make sure that dirty pages in the
79 # Show that the transaction has not been rolled back.
81 } {1 {cannot start a transaction within a transaction}}
88 # was not defined, then the statement would pass and the transaction
H A Dsavepoint2.test79 # transaction. In all cases open savepoint "one", which may or may
80 # not be a transaction savepoint, depending on whether or not a real
81 # transaction has been opened.
133 # database and COMMIT the open transaction, so that the next iteration
136 # The transaction being committed here may have been opened normally using
137 # "BEGIN", or may have been opened using a transaction savepoint created
H A Dinterrupt.test106 # Ticket #594. If an interrupt occurs in the middle of a transaction
107 # and that transaction is later rolled back, the internal schema tables do
110 # UPDATE: Interrupting a DML statement in the middle of a transaction now
111 # causes the transaction to roll back. Leaving the transaction open after
138 } {1 {cannot rollback - no transaction is active}}
H A Dwalcrash2.test23 # existed at one point: If a process crashes mid-transaction, it may have
25 # If the transaction were to be explicitly rolled back at this point, the
27 # if the process crashes, the transaction is implicitly rolled back and
41 # walcrash2-1.1: Create a database. Commit a transaction that adds 8 frames
45 # walcrash2-1.2: Have an external process open a transaction, add 8 entries
H A Dtkt3093.test48 # busy callback, commit the transaction in db. This should clear
62 # Start a write transaction on db.
74 # Verify that everything worked as expected. The db transaction should
75 # have gone first and added entry 2. Then the db2 transaction would have
H A Dtkt3718.test66 # caused the statement transaction belonging to the INSERT statement to
88 # statement transaction belonging to the INSERT statement to be rolled back.
120 # transaction can be successfully committed or reverted without
121 # affecting the parent statement transaction.
153 # The next set of tests, tkt3718-3.*, test that a statement transaction
154 # that has a committed statement transaction nested inside of it can
H A Dwaloverwrite.test31 # + Within a transaction, loop through the set of blobs 5 times. Update
42 # + Same thing, but before committing the statement transaction open
49 # step 3 (tn==1) and once where it already contains a transaction (tn==2).
80 db transaction {
116 db transaction {
H A Dwalblock.test67 # 1. Open a write transaction using client [db] in this process.
69 # 2. Attempt to commit the write transaction. Intercept the xShmBarrier()
80 # 5: Finish committing the transaction. Then wait for 0.5 seconds more.
82 # and that the snapshot it read included the transaction committed in
H A Dmalloc5.test78 # Test that the transaction started in the above test is still active.
94 # Commit the transaction and open a new one. Read 1 page into the cache.
96 # before the transaction is concluded.
107 # Conclude the transaction opened in the previous [do_test] block. This
207 # The following two test cases each execute a transaction in which
210 # the transaction.
214 # transaction execution.
362 # Now open a transaction and update 2 pages in the db2 cache. Then
367 # freed is page1 of db2. Because there is an open transaction, the
H A Dsavepoint.test186 # This block of tests - savepoint-3.* - test that when a transaction
188 # And that when a transaction savepoint is released, they are released.
195 execsql { SAVEPOINT "transaction" }
205 execsql { ROLLBACK TO "transaction" }
215 execsql { RELEASE "transaction" }
338 # using a second database handle, open a read-only transaction on the
340 # until after the read-only transaction has been closed.
344 # As above, except that the savepoint transaction can be successfully
345 # committed before the read-only transaction has been closed.
619 # a savepoint is open (it is not possible if any transaction is open).
[all …]
H A Dfts3shared.test43 # Open a write transaction and insert rows into the FTS3 table. This takes
62 # Verify that the first connection can commit its transaction.
68 # Verify that the second connection still has an open transaction.
78 # SQLITE_LOCKED error to be enountered when committing an FTS transaction.
81 # table is first read/written within a transaction, not later on.
H A Dpager1.test106 # Open a transaction and add a row using [db]. This puts [db] in
108 # read the database content as it was before the transaction was
125 # [db2] is left with an open transaction, but not a read-lock on
151 } {1 {cannot start a transaction within a transaction}}
216 # [db] is now able to commit the transaction. Once the transaction is
662 # file is deleted to commit the transaction.
696 # Check that the transaction was committed successfully.
748 # journal file to commit a transaction. The transaction modifies exactly
774 # Check the transaction was committed:
1721 # journalled by the current transaction.
[all …]
H A Dattach2.test99 # start a transaction on test.db even though test2.db is locked.
117 # when the write failed in the previous test, the transaction should
120 # Update for version 3: A transaction is no longer rolled back if a
132 } {1 {cannot commit - no transaction is active}}
334 # correctly when a multi-file transaction is committed or rolled back.
368 # Check that a database cannot be ATTACHed or DETACHed during a transaction.
381 # As of version 3.21.0: it is ok to DETACH from within a transaction
H A Dwal.test59 # wal-3.*: Test transaction rollback.
513 # Have [db2] open a write transaction. Then attempt to write to the
516 # Then open a read-transaction with [db]. Commit the [db2] transaction
676 # if frames must be written to the log file before a transaction is
904 # if a transaction is open on the database.
1032 # transaction, then append as may frames as are required to extend the
1033 # log file so that no part of the next transaction will be written into
1034 # a disk-sector used by transaction just committed.
1317 db transaction { db eval {
1450 # transaction (because of an incremental or auto-vacuum), that no
[all …]
H A Dvtab4.test44 # in an implicit transaction. Each should result in a single call
79 # Ensure xBegin is not called more than once in a single transaction.
93 # Try a transaction with two virtual tables.
130 # Try an explicit ROLLBACK on a transaction with two open virtual tables.
/sqlite-3.40.0/doc/
H A Dpager-invariants.txt10 the transaction has been written into the rollback journal and
13 (b) The page was a freelist leaf page at the start of the transaction.
16 the database file at the start of the transaction.
24 transaction other than the update of the transaction sequence
30 transaction.
54 equivalent to the database file at the beginning of the transaction.
56 (8) When a transaction is rolled back, the xTruncate method of the VFS
58 the beginning of the transaction. (In some VFSes, the xTruncate
70 of every transaction.
H A Dwal-lock.md39 If a read-only transaction is being opened on a snapshot, the CHECKPOINTER
40 lock is required briefly as part of opening the transaction (to check that a
51 * the transaction is an implicit one consisting of a single DML or DDL
53 * the transaction is opened using BEGIN IMMEDIATE or BEGIN EXCLUSIVE, or
57 In other words, in all cases except when an open read-transaction is upgraded
58 to a write-transaction. In that case a non-blocking lock is used.
80 * when an open read-transaction is upgraded to a write-transaction.
H A DF2FS.txt27 accumulates the entire transaction in heap memory, deferring all writes to the
28 db file until the transaction is committed.
30 When it is time to commit a transaction on a file that supports atomic
56 /* If we get there, the transaction has been successfully
/sqlite-3.40.0/tool/
H A Dspeedtest2.tcl127 runtest {25000 INSERTs in a transaction}
144 runtest {25000 INSERTs in a transaction}
161 runtest {25000 INSERTs in a transaction}
178 runtest {25000 INSERTs in a transaction}
195 runtest {25000 INSERTs in a transaction}

12345678