What Is a Dirty Read?
A dirty read occurs when one transaction reads a row that another transaction has modified but not yet committed. If the writing transaction later rolls back, the reader has acted on data that never officially existed. Isolation levels above read uncommitted prevent dirty reads.
Why it matters
Acting on uncommitted data can produce decisions based on changes that get undone. Understanding dirty reads guides which isolation level a workload actually requires.
Related guides
What Is a Phantom Read?A phantom read happens when a transaction re-runs a range query and finds new rows that another committed tra…
What Is a Transaction Isolation Level?An isolation level sets how much one transaction can see of others in progress, trading consistency guarantee…
What Is Optimistic Locking?Optimistic locking detects conflicting updates at commit time by checking a version field, rather than holdin…