Subject | Re: Transactions |
---|---|
Author | Stephen Boyd |
Post date | 2005-10-26T13:46:16Z |
The property is called CommitAction and if you have it set to
caFetchAll all rows for all open queries will be fetched on commit.
Change CommitAction to caClose or caInvalidateCursor and that won't
happen.
caFetchAll all rows for all open queries will be fetched on commit.
Change CommitAction to caClose or caInvalidateCursor and that won't
happen.
--- In IBObjects@yahoogroups.com, Robert martin <rob@c...> wrote:
>
> Hi
>
> Sounds likely :)
>
> What is this 'Fetch all on commit' property you are referring
to ? I
> close all my queries / tables straight after committing, should I
do
> this first as an easy fix?
>
>
> Rob Martin
> Software Engineer
>
> phone +64 03 377 0495
> fax +64 03 377 0496
> web www.chreos.com
>
> Wild Software Ltd
>
>
>
> Stephen Boyd wrote:
>
> >I've seen this happen in my code and the usual culprit is a query
that
> >returns a lot of rows. If you have that query set to 'fetch all
on
> >commit' then all those records get read before the commit takes
> >places. This doesn't happen when using BDE and auto commit. Are
you
> >sure that you haven't inadvertently structured a query is such a
way
> >that the result set is large even though you only want the first
record
> >(s)?
> >
> >
> >
> >
> >
> >
> >
> >
>
>_____________________________________________________________________
______
> >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
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>