Subject Re: Re: [IBO] Transaction->ReadOnly = true
Author Jason Wharton
It all depends on how that dataset is configured.... RefreshAction,
CloseAction, etc.
The rule of thumb is to always be concerned about your transactions, even
so, I've done all I can to insure things take care of themselves as much as
possible. I don't have it 100% yet.


----- Original Message -----
From: "Paul Hope" <paulhope@...>
To: <>
Sent: Monday, October 06, 2003 1:44 AM
Subject: Re: Re: [IBO] Transaction->ReadOnly = true

> Hi Helen
> >
> > It's not the transaction isolation that causes the OAT to get stuck.
> > having read-write transactions that don't get committed, or that use
> > CommitRetaining. If you have your read-write transactions in AutoCommit
> > mode, you are getting CommitRetaining, not hard Commits.
> >
> I am a little concerned by this and would like it clarified. Does this
> that if I just put a TIB_Query on a form with a Select statement, leave
> IB_Transaction as <default> then open the query and leave the form open my
> OAT will be stuck?
> Does it imply that every read-only operation should use a ReadOnly
> transaction and that every updating thing (TIB_Query, TIB_Cursor, TIB_DSQL
> etc) should not use AutoCommit?
> Regards
> Paul