[Solved] Transaction 1 reads a set of rows matching a condition. Transaction 2 updates one of those rows and commits. When Transaction 1 reads the same row again, it sees the updated value.... | SQL

SQL - Transactions and Data Integrity

Transaction 1 reads a set of rows matching a condition. Transaction 2 updates one of those rows and commits. When Transaction 1 reads the same row again, it sees the updated value. What phenomenon is this?

ANon-repeatable read

BPhantom read

CDirty read

DSerialization anomaly

Step-by-Step Solution

Solution:

Step 1: Identify the read behavior
Transaction 1 reads a row twice and sees different values due to Transaction 2's committed update.
Step 2: Match phenomenon
This is a non-repeatable read, where repeated reads return different data because of committed changes.
Final Answer:
Non-repeatable read -> Option A
Quick Check:
Repeated reads differ = Non-repeatable read [OK]

Quick Trick: Non-repeatable reads show changed data on repeated reads [OK]

Common Mistakes:

Confusing non-repeatable read with phantom read
Thinking dirty read applies after commit
Mixing serialization anomaly with read phenomena

Master "Transactions and Data Integrity" in SQL

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More SQL Quizzes

What phenomenon is this?

Step 1: Identify the read behavior

Step 2: Match phenomenon

Final Answer:

Quick Check:

Want More Practice?