Actually one of the wonderful things about firebird is its ability to
use multiple indexes in a query.

So if you had a table like "People" and a couple of fields "FirstName"
and "LastName", you may be compelled (if you aren't, just deal with my
poor example) to create an index on FirstName, one on LastName, and one
on FirstName & LastName. The last index here is redundant. Firebird will
happily use the Index on Firstname and Lastname at the same time.

Jason

Clay Shannon wrote:

> Is the db "smart enough" to automatically use the composite index in the
> case mentioned:
>
> Order by sort_order, empno, shiftdate, created desc
>
> ?
>
> Clay Shannon,
> Dimension 4 Software