Lines Matching full:transaction
280 ** ^If [sqlite3_close()] is invoked while a transaction is open,
281 ** the transaction is automatically rolled back.
724 ** current transaction. This hint is not guaranteed to be accurate but it
775 ** write ahead log and shared memory files used for transaction control
799 ** a write transaction to indicate that, unless it is rolled back for some
801 ** transaction. This is used by VACUUM operations.
877 ** of the sqlite3_vfs object changes in the transaction between
1796 ** that is inside an explicit transaction, then the entire transaction
1889 ** when SQLite is in the middle of a large transaction where all the
3015 ** ^Transaction control statements such as [BEGIN], [COMMIT], [ROLLBACK],
3041 ** statements that are holding a transaction open.
3415 ** or occurs outside of an explicit transaction, then you can retry the
3417 ** explicit transaction then you should rollback the transaction before
4462 ** transaction (errors including [SQLITE_FULL], [SQLITE_IOERR],
4464 ** transaction might be rolled back automatically. The only way to
4465 ** find out whether SQLite automatically rolled back the transaction after
4530 ** function to be invoked whenever a transaction is [COMMIT | committed].
4534 ** function to be invoked whenever a transaction is [ROLLBACK | rolled back].
4564 ** ^For the purposes of this API, a transaction is said to have been
4567 ** ^The rollback callback is not invoked if a transaction is
5256 ** commit if the transaction continues to completion.)^
5310 ** ^Closing a BLOB shall cause the current transaction to commit
6328 ** ^SQLite holds a write transaction open on the destination database file
6440 ** active write-transaction on the destination database is rolled back.
6527 ** its current transaction, either by committing it or rolling it back.
6536 ** when the blocking connections current transaction is concluded. ^The
6538 ** call that concludes the blocking connections transaction.
6542 ** concluded its transaction by the time sqlite3_unlock_notify() is invoked.
6576 ** When a blocking connections transaction is concluded, there may be
6591 ** connection Y's transaction to be concluded, and similarly connection
6592 ** Y is waiting on connection X's transaction, then neither connection
6600 ** callback on the conclusion of connection B's transaction, and connection
6602 ** A's transaction is concluded. ^Indirect deadlock is also detected, so
6605 ** C's transaction, where connection C is waiting on connection A. ^Any
6672 ** [write-ahead log] (i.e. whenever a transaction is committed in
6714 ** after committing a transaction if there are N or
6882 ** is able to roll back a statement or database transaction, and abandon
