A query in the current transaction can read data modified within another transaction but not yet committed. The database
engine does not issue shared locks when Read Uncommitted is specified, making this the least restrictive of the isolation levels.
As a result, it’s possible that a statement will read rows that have been inserted, updated or deleted, but never committed to
the database, a condition known as dirty reads. It’s also possible for data to be modified by another transaction between issuing
statements within the current transaction, resulting in nonrepeatable reads orphantom reads.
Submitted questions and answers are subject to review and editing, and may or may not be selected for posting, at the sole discretion of w3Sniff.
Get Started
Comments
Leave a Comment