Read committed isolation prevents dirty reads and lost updates while allowing unrepeatable reads and phantom reads during concurrent transaction execution. section 11.2.1
Its behavior can be summarized as follows:
- Blocks a transaction from reading data written by an uncommitted transaction. section 11.2.1
- Prevents two transactions from producing lost updates. section 11.2.1
- Allows a repeated query to observe changed values or newly matching rows after another transaction commits. section 11.2.1
- May use shared read locks and exclusive write locks, although locking strategies vary by database vendor. section 11.2.1
Table 11.1 ANSI isolation levels and the problems that they address (view table figure)
Compare read committed with read uncommitted, repeatable read, and serializable isolation across dirty reads, lost updates, unrepeatable reads, and phantom reads. section 11.2.1
