Subject | Re: CommitRetaining question |
---|---|
Author | Ali Gökçen |
Post date | 2005-10-08T16:57:14Z |
Ray,
its too easy to discover what happens in DB.
open two transaction in read-commited mode.
change something from T1 and do commit retaining.
then try to read this changes from T2 by reading same records.
change something again via T1, post it and kill its procesess or reset
the computer without any commit.
re-read changed data from T2.
what will you want to see?
Regards.
Ali
P.S. you can display current_transaction number in each step.
--- In firebird-support@yahoogroups.com, "yeohray" <yeohray@h...>
wrote:
its too easy to discover what happens in DB.
open two transaction in read-commited mode.
change something from T1 and do commit retaining.
then try to read this changes from T2 by reading same records.
change something again via T1, post it and kill its procesess or reset
the computer without any commit.
re-read changed data from T2.
what will you want to see?
Regards.
Ali
P.S. you can display current_transaction number in each step.
--- In firebird-support@yahoogroups.com, "yeohray" <yeohray@h...>
wrote:
>
> > Yes, eventually. The server will eventually be informed that the
> > connection is dead and the transaction status will be converted to
> rolled back.
>
> Thanks. I didn't realise the transaction would be rolled back. I
> thought the changes would still remain committed.
>
> Ray Mond
>