Subject | Re: [IBO] DMLCache |
---|---|
Author | Helen Borrie |
Post date | 2001-05-07T17:58:20Z |
At 05:45 PM 07-05-01 +0000, you wrote:
Between applications and open datasets - yes. If you have an open dataset that is within an uncommitted transaction which has an Isolation of tiReadCommitted, then DMLCaching will cause you to see the committed work of other transactions. Perhaps that is where the confusion arose. You will never see the uncommitted work of transactions in other applications.
Helen
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________
>--- In IBObjects@y..., Helen Borrie <helebor@d...> wrote:Oooh, I hope not! If it was in the TI Sheet on DMLCaching, it's a bug in the documentation and therefore down to me. Transactions are not "open", in the sense that, once committed or rolled back, they cease to exist.
>Hi Helen,
>
>thanks for your response. I have read anywhere, that DMLCaching would
>work between applications and open transactions.
Between applications and open datasets - yes. If you have an open dataset that is within an uncommitted transaction which has an Isolation of tiReadCommitted, then DMLCaching will cause you to see the committed work of other transactions. Perhaps that is where the confusion arose. You will never see the uncommitted work of transactions in other applications.
>I thought, if there is a way, that DMLCaching could work whileEach user (using a different user name, ONLY) can see the committed work of all other users, if his transaction's Isolation parameter is tiReadCommitted.
>transactions are not commited, maybe I have used wrong paremeters.
Helen
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________