Timeline for Advanced design question related to compound primary keys
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2014 at 13:10 | comment | added | e4ch | Thanks for your suggestions. For a), that won't work, because the table UserProduct only contains User-ID and Product-ID, but not Client-ID. How would you add a constraint that verifies that an entry with same Client-ID doesn't already exist? Only a trigger can do that, no constraint. For b) and c), if you add a trigger anyway, you don't need any other table at all. And yes, everything will be handled by stored procs anyway, so it's unlikely that wrong entries will ever exist. As you talked about the potential new table ProductClient, this gave me some ideas to argue. | |
| Apr 17, 2014 at 12:38 | history | answered | Michael Green | CC BY-SA 3.0 |