Re: Exclusive lock

From: "Piotr Wawrzyniak" <Piotr.Wawrzyniak@put.poznan.pl> > >I know that "Exclusive mode denies other processes both read and write >access to the table." (from manual). But is any possibility to allow other >transaction to make select (and view old values) before we make commit or >rollback (as is possible in Oracle). > >For example: >begin work; > insert into table A values (B);>-- Another transaction select >commit work; SET ISOLATION TO DIRTY READ? _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.

From Obnoxio The Clown > >I know that "Exclusive mode denies other processes both read and write > >access to the table." (from manual). But is any possibility to allow other > >transaction to make select (and view old values) before we make commit or AND VIEW OLD VALUES (old - before update) > >rollback (as is possible in Oracle). > > > >For example: > >begin work; > > insert into table A values (B);> >-- Another transaction select > >commit work; > > SET ISOLATION TO DIRTY READ? Maybe I not write everything, I'm not interested in DIRTY READ because I want situation than uncommited changes are invisible. I want situation like in Oracle: 1. before COMMIT I not see changes but I can SELECT old values. 2. past COMMIT I see new values. 2. past and before ROLLBACK I don't see any changes. (So the DIRTY READ isolation can't be set). Piotrek Wawrzyniak