KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
Say you have a Many-Many table between Artists and Fans. When it comes to designing the table, do you design the table like such: ArtistFans ArtistFanID (PK) ArtistID (FK) UserID (FK) (ArtistID and UserID will then be contrained with a Unique Constraint to prevent duplicate data) Or do you build use a compound PK for the two relevant fields: ArtistFans ArtistID (PK) UserID (PK) (The need for the separate unique constraint is removed because of the compound PK) Are there are any advantages (maybe indexing?) for using the former schema?
Tags (comma-separated)
Save Edits
Cancel