> >I understand the way to do it now is table reservation. It has the

aditional

> >work of reserving/unreserving new touched tables when the programmer
> >modifies the client application.
>
> Unreserving?

Unreserving tables that I now don't touch after modifications to the code.

> And yes, table locking is serializable and should be so under
> 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.

Yes, for example some users can think repeteable-reads means records readed
can't be touched by other transactions, this is true only in locking model
database systems.