Subject | Re: [IBO] transaction question: client ds |
---|---|
Author | Jason Wharton |
Post date | 2002-09-11T23:01:56Z |
CachedUpdates is what you want for this.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
-- We may not have it all together --
-- But together we have it all --
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
-- We may not have it all together --
-- But together we have it all --
----- Original Message -----
From: "Boris Schlüszler" <boris@...>
Newsgroups: egroups.ibobjects
To: <IBObjects@yahoogroups.com>
Sent: Friday, August 09, 2002 3:38 PM
Subject: [IBO] transaction question: client ds
> 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