Where does dirty collide?

In database concurrency control, a dirty read occurs when one transaction reads data written by another transaction that has not yet committed, so the reader may act on values that are later rolled back and never existed in any committed state. Berenson and colleagues' 1995 A critique of ANSI SQL isolation levels re-defined this and the other isolation anomalies precisely in terms of conflicting operation histories. The referent is a concurrency anomaly (exposure to uncommitted writes) ruled out by higher isolation levels, sharing only the adjective with a bond's dirty price or a data set's dirty records.[1]

Unit

An uncommitted value exposed to a concurrent reader

Recovery means

Avoided by read-committed or higher isolation, which hides uncommitted writes from other transactions

Measured by

Identified in a transaction history where a read depends on a write that is later aborted

In fixed-income finance, the dirty price (or full price) of a bond is its quoted clean price plus the interest accrued since the last coupon date, and it is the amount a buyer actually pays on settlement. Fabozzi's Bond markets, analysis, and strategies sets out the clean/dirty distinction and the accrued-interest calculation used in settlement. The referent is a pricing convention (the invoice price including accrued interest) measured in currency per unit of face value, sharing only the word “dirty” with the database anomaly and the data-quality defect.[2]

Unit

The invoice price of a bond including accrued interest

Recovery means

Not applicable

Measured by

Computed as the clean price plus interest accrued since the last coupon date