Subject | Re: [IBO] Re: SQL plan in TIBOQuery |
---|---|
Author | Jason Wharton |
Post date | 2003-02-04T18:05:55Z |
In this case it has to remain as-is because in all cases for that feature to
be effective it needs to leverage the index.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
-- We may not have it all together --
-- But together we have it all --
be effective it needs to leverage the index.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
-- We may not have it all together --
-- But together we have it all --
----- Original Message -----
From: <hubert@...>
To: <IBObjects@yahoogroups.com>
Sent: Tuesday, February 04, 2003 2:40 AM
Subject: [IBO] Re: SQL plan in TIBOQuery
> --- In IBObjects@yahoogroups.com, "Jason Wharton" <jwharton@i...>
> wrote:
> > Also remember, if it is pulling in too many indexes there are
> tricks you can
> > do to suppress their inclusion. For example:
> >
> > SELECT *
> > FROM ATABLE
> > WHERE ACOLUMN + 0 = AVALUE
> >
> > Adding the + 0 will make it so that the optimizer will not include
> an index
> > for that column.
>
> The WHERE clause is provided by the OrderingLinks/OrderingItems
> feature and not by me.
>
> Regards,
>
> Hubert Krukowski