Dirty Read

A dirty read observes data written by a transaction that has not committed. If that transaction rolls back, the reader has acted on a value that was never durably accepted.

This can create incorrect reports or trigger downstream actions based on temporary state. Isolation levels normally describe whether this behavior is allowed, but a product’s implementation matters: similarly named levels do not necessarily expose the same anomalies in every database.