MySQL database transaction ISOLATION LEVEL

Http://www.cnblogs.com/wenfeng762/archive/2011/11/06/2237253.html

http://xm-king.iteye.com/blog/770721

Read uncommited reading dirty data problem non-repeatable read and Phantom read

Read commited non-repeatable reading of Phantom read

REPEATABLE READ Phantom Reading

Serilizable

Read dirty data, because a transaction read the B transaction changed data, but not yet committed, if B rollback, then a read is dirty data

Non-repeatable read, transaction A has a SELECT statement, query two times, b transaction modified the relevant data, the first time before the B transaction commits, the second after the B transaction commits, then two reads the data inconsistent

Phantom Read, transaction A has a SELECT statement, queries two times, two queries, B transactions insert a few data, the second time than the first read more than the number of data bars. However, as noted in the second link above, the database is different from the implementation of the isolation level, so it can only be said that phantom reading can occur

MySQL database transaction ISOLATION LEVEL