Core Concept Mastery • DBMS Module
Let's use an Online Shopping analogy strictly.
Active: You are browsing, adding items to the cart. The connection is open.
Partially Committed: You clicked "Pay Now". The money left your bank, but the store hasn't generated the invoice yet. It's in limbo.
Committed: The order is Confirmed. You got the email. Even if you turn off your phone now, the order is safe.
Failed: You clicked "Pay", but the internet cut out.
Aborted: The system sees the failure and auto-refunds your money to the cart. It "rolls back" to before you clicked Pay.
We need to track exactly where we are so we know whether to "Rollback" (undo) or "Commit" (save) if something goes wrong.
It's like online shopping. Adding to cart (Active) -> Checkout (Partial) -> Payment Success (Committed). If card declines -> Cancel Order (Aborted).
All or Nothing
Rules are Sacred
Queue, don't crowd
Saved forever
"A transaction reaches which state after the final statement has been executed?"
Partially Committed.