--- In firebird-support@yahoogroups.com, Svein Erling Tysvaer
<svein.erling.tysvaer@k...> wrote:

> I am still confused as to why the
> optimizer changed its suggested plan due to a non-indexed field

Set, OR-based conditions always were weak place in IB/FB optimizer,
seems you found one more surprise :)

> and

why it

> insisted on doing this by itself and refused the very same plan when

I

> hardcoded it.

This one I registered as bug 555875 more than a year ago. It is
fixed in FB1.5. Seems Arno even did'nt noticed this fact doing general
improvement - status is still "Opened" :)) Perhaps first is fixed too,
try FB1.5.

Best regards,
Alexander.