Subject composite primary key
Author Fabrice Aeschbacher

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?

Best regards,
Fabrice Aeschbacher