Say I have two separate transactions.
In the first transaction, I update a row in a table, but have not yet
committed the change.
Now, I would like for the second (and all other) transactions to see
the *previous value* (which is the last value committed) of the changed
row,
up until the first transaction actually commits the change.
However, this does not seem to be possible.
I can choose to either read the current uncommitted value,
with isolation level set to read uncommitted, or wait until the
change is committed. With isolation set to read committed, the
reading transaction can't access the row at all until the first
transaction commits or rolls back its changes.
Is there any way to get the desired behavior of being able to read the
old values up until the new values are actually committed?
============================================================
Roger S. Reynolds
email: rsr@rogerware.com rsr@softix.com
Web: http://www.rogerware.com