Subject | Re: [firebird-support] Using index-optimizer with max(xfield) function |
---|---|
Author | Jerome Bouvattier |
Post date | 2003-11-20T09:37:43Z |
Helen,
In such a situation, mySQL will actually maximize the ASC index. As
Alexander told me, FB can't behave so because of the unidirectional nature
of its b-tree indices.
Fine. I don't know much about index structures. To satisfy my curiosity, can
you tell me what sibling advantage(s) bring unidirectional indices ?
There cannot be only limitations ... right ? ;-)
Thanks.
--
Jerome
In such a situation, mySQL will actually maximize the ASC index. As
Alexander told me, FB can't behave so because of the unidirectional nature
of its b-tree indices.
Fine. I don't know much about index structures. To satisfy my curiosity, can
you tell me what sibling advantage(s) bring unidirectional indices ?
There cannot be only limitations ... right ? ;-)
Thanks.
--
Jerome
----- Original Message -----
From: Helen Borrie
To: firebird-support@yahoogroups.com
Sent: Thursday, November 20, 2003 8:55 AM
Subject: Re: [firebird-support] Using index-optimizer with max(xfield)
function
> >Select max(aField) from aTable
> >
> >and there is an index on afield, it is not used. How can I use an
> >index wit above statement ???
> The optimizer will use a descending index for this query, if one
> exists. It would never use an ascending index.