santhanapandi

• Jul 1st, 2013

 

The SQL standard defines four levels of transaction isolation in terms of three phenomena that must be prevented between concurrent transactions. These undesirable phenomena are:

Dirty read
A transaction reads data written by a concurrent uncommitted transaction.

Nonrepeatable read
A transaction re-reads data it has previously read and finds that data has been modified by another transaction (that committed since the initial read).

Phantom read
A transaction re-executes a query returning a set of rows that satisfy a search condition and finds that the set of rows satisfying the condition has changed due to another recently-committed transaction.

supriya

• Dec 8th, 2017

 

You can set isolation level as read uncommited.