Steve,

> In their infinite wisdom the FB developers seem to have decided to
> change the way the indices generated for primary key constraints are
> named.

This change was in SPECIFIC response to long standing user/developer
complaints about the previous index names.

> This is arguably the way it should have been all along but it
> breaks my application. I use the primary key names in PLAN clauses
> in my stored procedures.

Martijn has made my point on this subject, so I won't repeat it.

> Is there some compatibility option that will suppress this
> new behaviour?

There is the ability to specify the index name in the constraint DDL --
I don't have the details handy -- check the Firebird Devel archives or
the draft RC5 release notes for details.


Sean