Unrepeatable Read: why a problem
From: Ravi <ra.ravi.rav_at_gmail.com>
Date: 27 Apr 2007 08:18:31 -0700
Message-ID: <1177687111.583528.87470_at_t39g2000prd.googlegroups.com>
Suppose I've got a part of schedule as:
...
...
Date: 27 Apr 2007 08:18:31 -0700
Message-ID: <1177687111.583528.87470_at_t39g2000prd.googlegroups.com>
Suppose I've got a part of schedule as:
...
T1 : Read(X) T2 : Write(X) T1 : Read(X)
...
We call this unrepeatable read problem as T1 does not get the same
value of X.
But I've got an objection. Why see it as a problem? Our operations may
want us to make T1 read the value of X overwritten by another
operation (ACID violation).
Then why would any transaction would read the data again, and moreover
would like to see the same data which was already with it in the
buffer.
Doesn't make sense.
Received on Fri Apr 27 2007 - 17:18:31 CEST