Subject | Re: Optimization Question |
---|---|
Author | Alexander V.Nevsky |
Post date | 2004-02-19T19:52:56Z |
--- In firebird-support@yahoogroups.com, Jakub Hegenbart
<Kyosuke@s...> wrote:
in the query plan that it's going to ORDER the rows using index, one
can't tell whether it's going also to FILTER using the index or not.
This sentence would imply that it IS possible and that it happens.
I'll take one more look into the book, but the opposite wouldn't make
any sense for me since it's trivial to use the ORDERED-employed index
also to filter rows.
Jakub, seems I was'nt precise enough and you forgot context of
discussion. I meant some segments to filter, another segments to sort.
Dunno. Hope yes, I often use explicit plans though most of
developers call them 'ugly hack' ;)
Best regards,
Alexander.
<Kyosuke@s...> wrote:
> I'm not sure I understand. You say that FB can't use the same indexboth to join/filter and to sort...
>- if i remenber it correctly - there's a statement that if FB reports
> But in a book I have (the only one in Czech, written by Pavel Cisar)
in the query plan that it's going to ORDER the rows using index, one
can't tell whether it's going also to FILTER using the index or not.
This sentence would imply that it IS possible and that it happens.
I'll take one more look into the book, but the opposite wouldn't make
any sense for me since it's trivial to use the ORDERED-employed index
also to filter rows.
Jakub, seems I was'nt precise enough and you forgot context of
discussion. I meant some segments to filter, another segments to sort.
> Yes, I'm aware of these limitations. Is it going to change insometime in the future?
Dunno. Hope yes, I often use explicit plans though most of
developers call them 'ugly hack' ;)
Best regards,
Alexander.