Lines Matching refs:transaction

31 # 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
82 #     * The current transaction may be rolled back. In this case a hot-journal
103 # transaction rollback is required, all other vdbe's are aborted.
124 # READ_UNCOMMITTED query, we have to make sure the transaction or statement
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.
191 # back any active transaction if malloc() fails. It must rollback the statement
192 # transaction only.
196   # value indicating if the statement may cause transaction rollback when
208 #     A shorthand test to see if a transaction is active or not. The first
222 # in a single-statement transaction on an empty database. Not too much can go
240 # transaction. test that the table is unpopulated before running the inserts
445 # Test some schema modifications inside of a transaction. These should all
446 # cause transaction rollback if they fail. Also query a view, to cover a bit
495 # Test a simple multi-file transaction