intermediate~4h
Transactions — ACID, COMMIT, ROLLBACK, SAVEPOINT
A transaction is a logical unit of work that must execute completely or not at all. Transactions ensure database integrity even in the face of errors, crashes, and concurrent access.
Learning objectives
- Explain each ACID guarantee in terms of a concrete failure it exists to prevent.
- Trace what happens to a partially-completed transaction if the application crashes before COMMIT.
- Use SAVEPOINT to roll back part of a transaction without discarding the whole thing.
This is a Pro chapter
Sign in, then upgrade to Pro or Power to unlock this and the full Databases Mastery library.
Transactions — ACID, COMMIT, ROLLBACK, SAVEPOINT