From: "Ann W. Harrison" <aharrison@...>
Sent: Friday, July 27, 2001 9:00 AM

>
> Aside from making steam come out of my ears? Undoes the transactions
> changes without closing open cursors.
>

OK, I guess we could go round and round on this issue without resolving much
because data is accessed in different ways for different things. But it
still leaves open the question "If you don't have a non-data-aware method of
storing data so that a transaction can be closed immediately after pulling
that data, what is the most feasible, plausible and acceptable settings for
a transaction that needs to be left open while browsing data even if for a
single record?"

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.


Comments?
Woody