Hi,
I was asking about experience with optimistic locking a few days ago. Has
really nobody done that before (as the non responses appear to me).
Problem was I can't use a "locking field" and couldn't find anything I can
use to produce a "select for update".
Lasse
|---------+----------------------------------------->
| | Lasse |
| | Lambrecht/IS-LF1/Allianz-Leben|
| | @ALLIANZ-DE |
| | |
| | 19.01.04 17:24 |
| | Bitte antworten an "OJB Users |
| | List" |
| | |
|---------+----------------------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| An: [EMAIL PROTECTED]
|
| Kopie:
|
| Thema: Optimistic locking / select ... for update
|
>-------------------------------------------------------------------------------------------------------------------------------|
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
