Reread value is an application-level concurrency technique for sagas. Before overwriting a record, a transaction rereads it and aborts if the value changed since the earlier read. section 9.3.2
The technique addresses missing isolation in multi-database sagas by preventing dirty writes. It belongs with other application-level countermeasures for anomalies such as lost updates, dirty reads, and fuzzy reads. section 9.3.2 section 9.4
Use reread value when an update must verify that its earlier view remains valid:
- Read the record during the transaction. section 9.3.2
- Reread the record immediately before overwriting it. section 9.3.2
- Abort rather than overwrite when the record has changed. section 9.3.2
