Subject | Please help - can CommitAction := caFetchAll solve it? |
---|---|
Author | Andreas Bednarek |
Post date | 2004-04-21T09:12:43Z |
Hello!
I try to solve why after a record is inserted to a dataset it is not
immediately visible when reading it. AutoCommit is true for all my TIBOTable
components.
In some parts of my application it is necessary to see always the most
actual content of the datasets. I tried to set caFetchAll for the
CommitAction property and it seems it helped, but I in fact don't know what
this value does.
The questions are:
1. Can caFetchAll solve my problem, won't there be some problem with
increased network traffic or so?
2. Is there some other solution for this? (I don't understand why a record
shouldn't be immediately visible there should be no blocking transactions or
whatever, I think).
Thank you very much!
Andreas
I try to solve why after a record is inserted to a dataset it is not
immediately visible when reading it. AutoCommit is true for all my TIBOTable
components.
In some parts of my application it is necessary to see always the most
actual content of the datasets. I tried to set caFetchAll for the
CommitAction property and it seems it helped, but I in fact don't know what
this value does.
The questions are:
1. Can caFetchAll solve my problem, won't there be some problem with
increased network traffic or so?
2. Is there some other solution for this? (I don't understand why a record
shouldn't be immediately visible there should be no blocking transactions or
whatever, I think).
Thank you very much!
Andreas