Nonrepeatable read
A nonrepeatable read is a concurrency anomaly in which repeated reads of the same data within a transaction return different values after another transaction modifies it.
Java Persistence with Spring Data and Hibernate epub
An unrepeatable read is a transaction anomaly in which a repeated read of the same data returns a different value because another transaction committed a modification.
- How it is used
- Frames a transaction anomaly for selecting an appropriate database isolation level.
- How deep it goes
- Defines the anomaly and demonstrates its timing, then compares isolation levels without detailing database locking internals.
- Examples
- Uses a highest-bid value read twice while another transaction updates and commits it between reads.
- What you can do after
- Evaluate isolation choices by determining whether they prevent nonrepeatable reads and what performance costs higher isolation brings.
Read how Java Persistence with Spring Data and Hibernate epub explains nonrepeatable read →
Microservices Patterns, Second Edition
A fuzzy read is a concurrency anomaly in which repeated reads of the same data return different values because another transaction modifies it between reads.
- How it is used
- Identifies a concurrency anomaly that can arise when sagas interleave across services.
- How deep it goes
- Defines the changed-value condition but does not trace a dedicated instance or prescribe a specific remedy.
- What you can do after
- Understand how concurrent saga steps can read different committed values after an intervening update.
Read how Microservices Patterns, Second Edition explains nonrepeatable read →
Also covered in
- 100 SQL Server Mistakes and How to Avoid Them
- The Coder CafeIn early access (MEAP)
- Latency
What to know first
- database transactionA database transaction is a bounded unit of database operations whose changes are treated as one logical whole, typically committed or rolled back together.
- SQLSQL is a standardized declarative language for defining, querying, and manipulating data in relational database systems.
Related concepts
- repeatable read isolation leveladdressed by · Repeatable read is a database transaction-isolation level that prevents a transaction from observing changes to data it has already read during that transaction.
- isolationaddressed by · Isolation is the separation of components, processes, resources, or contexts to limit interaction, interference, or the propagation of effects between them.
- snapshot isolationaddressed by · Snapshot isolation is a transaction-isolation method in which each transaction reads a consistent versioned snapshot of committed data while concurrent writes are isolated from that view.
- versioningaddressed by · Versioning is the practice of assigning or maintaining identifiable revisions of artifacts over time so their changes, histories, or compatibility can be tracked.
Questions about nonrepeatable read
What is nonrepeatable read?
A nonrepeatable read is a concurrency anomaly in which repeated reads of the same data within a transaction return different values after another transaction modifies it.
Which Manning books explain nonrepeatable read?
Java Persistence with Spring Data and Hibernate epub and Microservices Patterns, Second Edition.
What should I know before learning nonrepeatable read?
Manning books that teach nonrepeatable read usually introduce database transaction and SQL first.
What is nonrepeatable read also called?
Nonrepeatable read is also called fuzzy read.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

