Hi All

We are using Firebird 1.0.0 and we observe with IbPLANAnalyser that in
queries with many joins and on tables that have primary key, unique key
and foreign keys defined in order to force relational integrity,
the optimiser consistently is choosing wrong PLAN's
PLAN's that make use of indexes of unique constraints or foreign keys
and have a bad performance

I read somewhere in a newsgroup that Interbase was supposed not to
make use of indexes that have low selectivity.
Apparently this is not true for Firebird 1.00

Is this a bug ? Are there versions of Interbase or Firebird that do
not have this behaviour ?

best regards
Tanno

[Non-text portions of this message have been removed]