Subject | MAX() wants a DESC index ? |
---|---|
Author | Jerome Bouvattier |
Post date | 2003-11-18T09:57:20Z |
Hello all,
I am currently maintaining/pumping big tables with millions of records and
sometimes want to know infos like the biggest ID assigned. (IDs are not
generated by myself)
With FB (1.5 RC6), I noticed the MAX(<a_field>) needs a DESC index on
<a_field> to actually make use of an index.
I issued the same test on MSSQL 2000 & mySQL and seem to maximize the ASC
index if exists.
This makes a query such as SELECT MAX(ID) FROM PRODUCT return immediately
when FB needs 30 s.
Can someone enlight on why such a behaviour, if normal ?
Many thanks.
--
Jerome
I am currently maintaining/pumping big tables with millions of records and
sometimes want to know infos like the biggest ID assigned. (IDs are not
generated by myself)
With FB (1.5 RC6), I noticed the MAX(<a_field>) needs a DESC index on
<a_field> to actually make use of an index.
I issued the same test on MSSQL 2000 & mySQL and seem to maximize the ASC
index if exists.
This makes a query such as SELECT MAX(ID) FROM PRODUCT return immediately
when FB needs 30 s.
Can someone enlight on why such a behaviour, if normal ?
Many thanks.
--
Jerome