Hi all,

for a webbased application I need an optimistic locking mechanism. My
application uses an existing database, so I can't (and don't want) add an
extra locking column to each table.
How are you others handle this?
Of Course, I can do the optimistic locking by myself. Saving the original
object somewhere and reread and compare it before saving. But in this case
in need a "select...for update" SQL to be sure the row is not modified in
the meantime. How can I do that with OJB (PB-API prefered).

Regards
Lasse




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to