Subject | transaction question: client ds |
---|---|
Author | Boris Schlüszler |
Post date | 2002-08-17T20:15:32Z |
Hi!
What would be the proposed way, to set up a behaviour like this:
1. Read one row into memory (select * from table)
2. manipulate it in memory (takes a long time, so I don't want to have
in within transaction)
3. if row has the same version number as before: write new data back to
table (update table set ...)
else croak
I guess it can be done with a special setup of transaction isolation
level and pessimistic locking.
Currently I often run into deadlock errors.
I'm pretty sure I'm just too dumb to find out?
Can anyone give me a hint?
Regards, Boris
What would be the proposed way, to set up a behaviour like this:
1. Read one row into memory (select * from table)
2. manipulate it in memory (takes a long time, so I don't want to have
in within transaction)
3. if row has the same version number as before: write new data back to
table (update table set ...)
else croak
I guess it can be done with a special setup of transaction isolation
level and pessimistic locking.
Currently I often run into deadlock errors.
I'm pretty sure I'm just too dumb to find out?
Can anyone give me a hint?
Regards, Boris