Which two transaction isolation levels guarantee that you get the same results both times?

You have a transaction that queries a table at the beginning of the transaction and performs
the same query later.
Which two transaction isolation levels guarantee that you get the same results both times?

You have a transaction that queries a table at the beginning of the transaction and performs
the same query later.
Which two transaction isolation levels guarantee that you get the same results both times?

A.
Repeatable read

B.
Read committed

C.
Read uncommitted

D.
Single user

E.
serializable

Explanation:
Reference:
http://dev.mysql.com/doc/refman/5.0/en/commit.html

Show Hint

Leave a Reply 3

Your email address will not be published. Required fields are marked *

zz

zz

A E

http://dev.mysql.com/doc/refman/5.0/en/commit.html

The WITH CONSISTENT SNAPSHOT option starts a consistent read for storage engines that are capable of it. This applies only to InnoDB. The effect is the same as issuing a START TRANSACTION followed by a SELECT from any InnoDB table. See Section 14.2.8.2, “Consistent Nonlocking Reads”. The WITH CONSISTENT SNAPSHOT option does not change the current transaction isolation level, so it provides a consistent snapshot only if the current isolation level is one that permits consistent read (REPEATABLE READ or SERIALIZABLE)

Reply