Hi David, That would require studying openjpa internals in great depth, and I'm too time poor I'm afraid.
dezzio wrote: > > Hi Philip, > > Your suggestion might work. Would you like to create the proof? > > Cheers, > > David > > > Philip Aston wrote: >> Hi David, >> >> EL does an update for each read lock at commit time, setting its version >> column to the same value. See my other post - I agree that SELECT FOR >> UPDATE >> is not appropriate for read locks, and I instead suggest a third >> approach; >> that is to do the optimistic lock checks for read locks after the INSERT, >> DELETE, and UPDATES for the transaction. >> >> - Phil > -- View this message in context: http://n2.nabble.com/Is-the-implementation-of-lock%28LockModeType.READ%29-correct--tp2272546p2350288.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
