db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Bengtson <e...@jpox.org>
Subject RE: Optimistic locking - not 100% reliable without triggers?
Date Tue, 14 Mar 2006 12:16:02 GMT
Jorg,

Quoting Eric Samson <eric@xcalia.com>:
>
> One common portable solution to this is to acquire locks during the conflict
> detection step (using SELECT for UPDATE instead of simple SELECT).
>

This should work in JPOX. If it does not raise a bug.

> Another approach could be to perform the conflict detection and the update
> at the same time (statement like “UPDATE WHERE pk=OID AND TS=ts”), but it
> raises some concerns for the conflict resolution (most JDBC drivers are not
> able to indicate which rows raised an exception).
>
>

This is not implemented in JPOX due to the issue Eric explained.



Mime
View raw message