Lines Matching full:roll
7432 ** is able to roll back a statement or database transaction, and abandon
8898 ** roll back. See comments for function writeMasterJournal() in pager.c
28377 ** will not roll back - possibly leading to database corruption.
38827 ** lock on the database file before attempting to roll it back. See function
39142 ** to roll the journal back, the database could be corrupted. The additional
39657 ** definitely roll back, so just return SQLITE_OK and report a (nul)
40272 ** file has been finalized it is not possible to use it to roll back a
40419 ** will roll it back.
42152 ** Syncing a hot-journal to disk before attempting to roll it back ensures
42181 ** is made to roll it back. If an error occurs during the rollback
42208 ** database and close the journal file without attempting to roll it
42316 ** hot-journal rollback following recovery. It may roll back all
43031 ** will not roll it back.
43218 ** other connection managed to get in and roll it back before
43262 ** or roll back a hot-journal while holding an EXCLUSIVE lock. The
43568 ** when opening a hot journal file to roll it back.
43709 ** This is because in those states the code to roll back savepoint
44878 ** to exist, in case the transaction needs to roll back. Use pPgOld
58204 /* If a transaction is still open on the Btree, roll it back. */
61389 roll
61676 /* We are forced to roll back the active transaction. Before doing
67650 ** Set the database auto-commit flag to P1 (1 or 0). If P2 is true, roll
67749 ** VDBE to be rolled back after an error without having to roll back the
113271 ** So it needs to be freed here. Todo: Why not roll the temp schema into
