db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francois Orsini" <francois.ors...@gmail.com>
Subject Re: Derby row locking semantic
Date Thu, 18 Jan 2007 22:59:29 GMT
Correct - That is actually how Sybase ASE behaves (non-MVCC model).

On 1/18/07, Øystein Grøvlen <Oystein.Grovlen@sun.com> wrote:
>
>
> I think most database systems that do not have multiversion concurrency
>   will behave as describe.  When a scan encounters a exclusively locked
> row, it will generally not know whether the uncommitted operation is an
>   insert or an update.   For the latter, the row cannot be skipped since
> its previous version should be included in the result set if the
> transaction that updated the row is rolled back.
>
> --
> Øystein
>

Mime
View raw message