Subject | Re: [ib-support] Re: Full table scan |
---|---|
Author | Danny Garcia Hernandez |
Post date | 2002-06-25T12:41:49Z |
Magnus:
As i was saying before, plan can be used, many times if you know the
interbase behavior and tables, using plans improve your performance, the
problems are when you don�t know the way to hit the optimizer because your
select sintax is outside of your reach (view for example). Plans clause
don't have enough documentation because don't have many things to say.
You can join index inside plan, you can use order inside plans, and other
things, but i prefer you show some example before advice about it.
Regards Danny
""semprolbat"" <semprolbat@...> escribi� en el mensaje
news:af9i9j+3jov@......
As i was saying before, plan can be used, many times if you know the
interbase behavior and tables, using plans improve your performance, the
problems are when you don�t know the way to hit the optimizer because your
select sintax is outside of your reach (view for example). Plans clause
don't have enough documentation because don't have many things to say.
You can join index inside plan, you can use order inside plans, and other
things, but i prefer you show some example before advice about it.
Regards Danny
""semprolbat"" <semprolbat@...> escribi� en el mensaje
news:af9i9j+3jov@......
>
> > SELECT *
> > FROM SWEDEN
> > WHERE (NAME = 'MAGNUS' or 1=0)
>
> Does not seem to give the wanted effect, even when I switch tables
> from SWEDEN to NORWAY, which of course er mye bedre.
>
> I've come across the PLAN statement, and some testing gave impressive
> improvement in execution speed.
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>