Hi Fabrice,

> I am converting an existing (sql server) db into firebird. The
> current db makes quite a big use of composite primary keys (i.e., PK
> = RuleId + ActionId, for example). I would prefer not to have such
> composite PK, even not for "relation" tables (when implementing a
> many-to-many relationship).
>
> In your opinion, is it worth getting rid of these composite PKs,
> given that it could lead to some change to the client application?
>
> Or do you think composite PKs are not annoying at all?

If the composite primary keys don't have a business meaning -
eg: ARTICLE_CODE etc - but are numeric already (surrogate
primary keys), then don't change them by introducing yet another
surrogate key. My bet is that the keys are fine.

Just IMHO of course.


With regards,

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