Subject Re: [ib-support] Deadlock and wait
Author Woody
From: "Robert F. Tulloch" <tultalk@...>
Sent: Friday, July 27, 2001 10:02 AM
> > Is there an acceptable method or should everything be changed to:
> >
> > 1. Start transaction and pull the data you need.
> > 2. Store the data somewhere. (this is the only difficult part, IMO)
> > 3. Close the transaction.
> > 4. Modify the data
> > 5. Start another transaction.
> > 6. Post changes.
> > 7. Close the transaction.
> > 8. Return to #1 if needed.
> Isn't this sort of client-dataset'ish?? Or cached updates??

Exactly my point. If you don't use this technique, then you are guaranteed
to leave your transactions open indefinately which is an IB-no-no to most.
If a user opens a form to see some information and walks off to lunch, the
transaction stays open even if they change no information. Isn't that
considered taboo? To me, I see no problem except in the OIT-OAT comparisons.
And even at that, unless a change is made, it doesn't affect the OIT, right?

I just can't see myself going through and changing all my data-aware stuff
to non-data-aware simply to be able to close the transaction when
reading/browsing. I already close it whenever the user goes to a different
record so I really can't see the advantages of going beyond that but maybe
I'm just missing something.