Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Comments on What are the pros and cons of a composite primary key versus a unique constraint?
Parent
What are the pros and cons of a composite primary key versus a unique constraint?
Let's say we have two tables A and B and a join table C that has foreign keys to both A and B and the combination of those foreign keys is unique.
One could either do a unique constraint or a composite primary key on those columns.
What would the pros and cons of either solution to this be?
Post
One could either do a unique constraint on those foreign keys or a composite primary key on those columns.
For elegance, canonicity, a primary key is necessary. You would initially have a primary key on those columns.
However, for sortability reasons, you would eventually use just a primary key on a single column ad-hoc created to be the id/key, so no, in the end you don't have a primary key on those columns, but a unique constraint.
0 comment threads