Dear whatever-your-name-is,

> In their infinite wisdom the FB developers seem to have decided to
> change the way the indices generated for primary key constraints are
> named. It used to be that they were named RDB$PRIMARYnn which was a
> pain in the butt, but if you were careful about the way you generated
> the database each constraint always got the same index name. It now
> appears that the index name of the primary key constraint is the same
> as the name of the constraint. 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. Obviously, these
> SPs will no longer compile under FB1.5.

This is EXACTLY the reason why you should NOT use a PLAN
clause.

Why not test your procedures with Fb1.5 - which has several optimizer
improvements - to see if you need to adjust the plan at all.


With regards,

Martijn Tonies
Database Workbench - the developer tool for InterBase & Firebird
Upscene Productions
http://www.upscene.com