Subject | Re: [IBO] Query - CommitAction property |
---|---|
Author | Nico Callewaert |
Post date | 2001-07-16T06:01:37Z |
Thanks Jason,
What is the best, fastest setting then to end the transaction, but
to keep the dataset open, so the data remain in the screen. Is that a
caRefreshKeys ?
Thanks, Greetings, Nico Callewaert
What is the best, fastest setting then to end the transaction, but
to keep the dataset open, so the data remain in the screen. Is that a
caRefreshKeys ?
Thanks, Greetings, Nico Callewaert
----- Original Message -----
From: Jason Wharton <jwharton@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, July 13, 2001 7:13 PM
Subject: Re: [IBO] Query - CommitAction property
> No, it wouldn't be the same. fetchall is what the BDE would do. Prior to
the
> commit or rollback it would bring all the records into the buffer so that
> the transaction could be ended.
>
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: "Nico Callewaert" <ncw@...>
> To: <ibobjects@yahoogroups.com>
> Sent: Friday, July 13, 2001 1:59 AM
> Subject: [IBO] Query - CommitAction property
>
>
> > Hi all,
> >
> > When I use CommitAction of TIB_Query = caFetchAll, would that be
> the same (in performance) as I use caClose and reopen the query again
after
> a commit ?
> >
> > Thanks,
> >
> > Nico Callewaert
> >
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>