|Subject||Re: [IB-Architect] Isolation level implemetation|
> >I understand the way to do it now is table reservation. It has theaditional
> >work of reserving/unreserving new touched tables when the programmerUnreserving tables that I now don't touch after modifications to the code.
> >modifies the client application.
> And yes, table locking is serializable and should be so underYes, for example some users can think repeteable-reads means records readed
> any definition. Note that the definitions of transaction isolation
> modes are often very badly written and reflect their authors'
> assumption that locking is the only possible mechanism.
can't be touched by other transactions, this is true only in locking model