> Why do you need an index for sorting, Stephane? Generally, indexes are > great for JOIN and WHERE clauses, not for sorting. Do you have > millions of records and cannot eliminate 99% of them through a WHERE > clause? If so, are all of the records of interest or only a fraction? > My guess is that there may be other ways to solve your problem that > involves a WHERE clause... >
thanks sven, but unfortunatly yes it's this : the result set contain million of records :( with the index it's can return in few milliseconds, without it's can return in few seconds that s unaceptable for us ... the only way i found for now is that when they sort to add a value "where xxx is not null" i things that programatiquelly it's can not be so hard to add in firebird the functionnality to use index and also put nul value at the end > Set > > [Non-text portions of this message have been removed]
