Subject | Re: minimizing transaction-open time |
---|---|
Author | Aage Johansen |
Post date | 2002-05-08T19:02:19Z |
Doug Chamberlin wrote:
(as you read from) - you have to control every record that can be affected
by the inserts/updates/deletes. Not impossible, but a chore.
I use the timer approach (with commit or rollback), but this isn't without
problems. I've found users returning from lunch and seeing their work has
been rejected (rollback) having assumed that whatever they were editing
(either in a grid or a separate form) has automagically been completed for
them! Result: the record was never entered into the database.
Regards,
Aage J.
> Actually a much better way isBut you'll have to worry about whether you are updating the same database
> Start trans
> Read record
> Commit
> Let user edit record taking all the time they want.
> When they save:
> Start trans
> Write updates
> Commit
(as you read from) - you have to control every record that can be affected
by the inserts/updates/deletes. Not impossible, but a chore.
I use the timer approach (with commit or rollback), but this isn't without
problems. I've found users returning from lunch and seeing their work has
been rejected (rollback) having assumed that whatever they were editing
(either in a grid or a separate form) has automagically been completed for
them! Result: the record was never entered into the database.
Regards,
Aage J.