Subject | Re: [IBO] Prepare confusion |
---|---|
Author | Frank Ingermann |
Post date | 2002-08-21T00:49:19Z |
Hi Scronkey,
Scronkey wrote:
won't need unprepare/prepare (from the top of my head, a simple Refresh should
do - not certain though atm). To make a whole new Where clause do an
InvalidateSQL/Refresh on your query and clear/feed the SQLWhereItems in the
OnPrepareSQL event.
in general, prepare/unprepare is somewhat "expensive" so avoid it if you can.
hth,
fingerman
--
-------------------------------------------------------------------------
when parsers parse, and compilers compile, then why don't objects object?
fingerbirdy - fingerman's door to Firebird
http://www.fingerbird.de
Scronkey wrote:
> Hi there.as long as it's just the *params* in the Where clause you want to change, you
>
> I'm still a little confused about the use of prepare/unprepare.
> Are these only needed on paramterized queries?
>
> My scenario is that I have a query which most of the time uses one
> where clause, but occasionally I need to do a sqlWhere.Clear and use
> a different where clause.
> Do I need to unprepare/prepare in this case?
>
> I am finding that it works fine without using prepare at all, but
> I'm not sure if it is correct (ie speed)
>
> When is an unprepare explicitly needed? Always before a prepare?
>
> Thanks for any info.
> Rgds,
> -Ryan
won't need unprepare/prepare (from the top of my head, a simple Refresh should
do - not certain though atm). To make a whole new Where clause do an
InvalidateSQL/Refresh on your query and clear/feed the SQLWhereItems in the
OnPrepareSQL event.
in general, prepare/unprepare is somewhat "expensive" so avoid it if you can.
hth,
fingerman
--
-------------------------------------------------------------------------
when parsers parse, and compilers compile, then why don't objects object?
fingerbirdy - fingerman's door to Firebird
http://www.fingerbird.de