Timeline for How to establish a Two-to-One table relationship (PK-FK-CK)?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2013 at 11:13 | comment | added | Phil | That also sounds great. But messages are independent of both Projects and People. I want to keep things "flexible", in case, say a person might moved from project A to B. Therefore, I believe your first suggestion with two separate tables is better to avoid modifying a message's Project_FK when such move occurs. | |
| Nov 8, 2013 at 10:43 | vote | accept | Phil | ||
| Nov 8, 2013 at 10:36 | comment | added | Allan S. Hansen | If People and Projects are connected, do you then need Message on Project? Then I'd think a Message could contain a Project FK and a relationship to People to tie it to a specific project; or maybe be connected to the ProjectsToPeople entirely instead? | |
| Nov 8, 2013 at 10:31 | comment | added | Phil | Hello @AllanSHansen. Thank you for your message. Projects and People also have a (n-m) relationship, which is handled with a "ProjectsToPeople" table. I suppose having 2 tables to assosciate is a better option. Thanks! | |
| Nov 8, 2013 at 9:26 | history | answered | Allan S. Hansen | CC BY-SA 3.0 |