The Life Cycle of a Transaction

In this lesson, you will learn how a transaction moves through specific states to ensure your data remains reliable from start to finish.

The Journey of a Transaction

Every transaction in a database follows a predictable path. Think of it like a traveler moving through a checkpoint: it begins with an idea, executes a series of actions, and ultimately reaches a final destination of either success or failure.

The Core States

1. Active: When a transaction starts, it enters the Active state. This is where it performs its read and write operations. Every SQL command executed within the transaction boundaries happens here.
2. Partially Committed: Once the final statement is executed, the transaction enters this state. While the operations are finished, the changes aren't yet "hardened" to the disk. The database is checking for integrity constraints and preparing the logs.
3. Committed: If everything goes well, the transaction transitions to Committed. Its changes are now permanent and durable.
4. Failed/Aborted: If an error occurs (like a constraint violation or a system crash) while the transaction is Active or Partially Committed, it moves to the Failed state. The database must then perform a rollback to undo any partial changes, officially moving the transaction to Aborted.

Visualizing the Lifecycle

Consider a bank transfer:

BEGIN TRANSACTION;
UPDATE Accounts SET balance = balance - 100 WHERE id = 1; -- Active
UPDATE Accounts SET balance = balance + 100 WHERE id = 2; -- Active
-- Final statement reached: Transitioning to Partially Committed
COMMIT; -- Transitioning to Committed

If the database crashed or the account balance dropped below zero after the first UPDATE but before the COMMIT, the database would recognize the error, halt the process, and move the transaction to Aborted. This ensures that we don't end up with a "half-finished" transfer where money leaves one account but never arrives at the other. By managing these transitions, the database upholds the principles of Atomicity and Durability that we discussed in our previous sessions.

Key Takeaway: A transaction is a finite state machine that must transition from Active to either Committed or Aborted to ensure the database remains in a consistent state.