Subject | Re: [ib-support] Deadlock and wait |
---|---|
Author | Ann W. Harrison |
Post date | 2001-07-27T14:00:34Z |
At 08:38 PM 7/26/2001 -0400, Robert F. Tulloch wrote:
it doesn't change the transactions view of data. Since my bias is that
anything that doesn't provide a consistent view of data is not a transaction,
read committed fails that metric too.
changes without closing open cursors.
Regards,
Ann
www.ibphoenix.com
We have answers.
>Hi:Actually, even with read committed, it doesn't release all resources and
>
> > Commit retaining solves neither problem. It doesn't release resources
> > and, in the case of a consistent transaction, doesn't update the
> > transaction's view of data.
>
> It does with readcommited.
it doesn't change the transactions view of data. Since my bias is that
anything that doesn't provide a consistent view of data is not a transaction,
read committed fails that metric too.
> What exactly then does this do?Aside from making steam come out of my ears? Undoes the transactions
>
>/**************************************
> *
> * i s c _ r o l l b a c k _ r e t a i n i n g
> *
> **************************************
> *
> * Functional description
> * Abort a transaction but keep its environment valid
> *
> **************************************/
changes without closing open cursors.
Regards,
Ann
www.ibphoenix.com
We have answers.