Hi:

> 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?"

My normal ones for browsing ar:

read_committed
rec_version
nowait

And for special things (Table specific) where I do an instantaneous access/update:

(Probably more than I need)
write
read_committed
no_rec_version
nowait
protected
lock_read=MEMBERS
protected
lock_write=MEMBERS

> 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??