Subject | Re: [IBO] Please help - can CommitAction := caFetchAll solve it? |
---|---|
Author | Andreas Bednarek |
Post date | 2004-04-21T10:05:51Z |
Thanks Helen, does that probably mean that caRefresh would do the same as
TIBOTable.RefreshRows? If so I probably can't use it, because with a table
with large record count my application became unusable with RefreshRows
because of very low performance.
On other tables it can be usable, which shall I use ten, caRefresh or
caRefreshKeys?
Thanks in advance
Andreas
TIBOTable.RefreshRows? If so I probably can't use it, because with a table
with large record count my application became unusable with RefreshRows
because of very low performance.
On other tables it can be usable, which shall I use ten, caRefresh or
caRefreshKeys?
Thanks in advance
Andreas
----- Original Message -----
From: "Helen Borrie" <helebor@...>
To: <IBObjects@yahoogroups.com>
Sent: Wednesday, April 21, 2004 11:32 AM
Subject: Re: [IBO] Please help - can CommitAction := caFetchAll solve it?
> At 11:12 AM 21/04/2004 +0200, you wrote:
> >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).
>
> The dataset is only a copy of what is in the database. IBO fools you to
> think you are inserting into the database. You're not, of course: IBO
> does that for you behind the scenes, by composing an INSERT statement
based
> on what you entered into the fields of the editing control.
>
> So, after the commit, to see the new database state INCLUDING your new
> record, you have to REFRESH the dataset - set CommitAction to caRefresh or
> caRefreshKeys.
>
> Helen
>
>
>
>
___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or
InterBase
> without the need for BDE, ODBC or any other layer.
>
___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info
papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links
>
>
>
>
>