Subject | RE: [IBO] Re: TIB_Query.next consume memory? |
---|---|
Author | John Tomaselli |
Post date | 2002-09-28T12:58:48Z |
If possible it would be beter to put this in a stored procedure.
John
-----Original Message-----
From: Aage Johansen [mailto:aagjohan@...]
Sent: Friday, September 27, 2002 4:53 PM
To: ibObjects@yahoogroups.com
Subject: [IBO] Re: TIB_Query.next consume memory?
anfisoft wrote:
And, as Thomas noted, a TIB_Cursor is better for this.
--
Aage J.
___________________________________________________________________________
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 !
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
John
-----Original Message-----
From: Aage Johansen [mailto:aagjohan@...]
Sent: Friday, September 27, 2002 4:53 PM
To: ibObjects@yahoogroups.com
Subject: [IBO] Re: TIB_Query.next consume memory?
anfisoft wrote:
>I think your 'open' is redundant - 'first' is sufficient.
> My really huge Query-result is about 130.000 records big. I have to
> look at each of the records for some reason and coded:
>
> with IB_Query1 do
> begin
> open;
> first;
> while not(eof) do
> begin
> // here some outcommented code
> next;
> end;
> close;
> end;
>
And, as Thomas noted, a TIB_Cursor is better for this.
--
Aage J.
___________________________________________________________________________
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 !
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/