Timeline for Should I split this large table into three smaller tables?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 14, 2015 at 4:21 | comment | added | Jim | All users will have one main photo and optionally one or more other public photos and one or more other private photos. Thanks. | |
| Oct 14, 2015 at 3:22 | comment | added | Coder Absolute | I have re-read the question again and you have mentioned "All users will have at least one main photo" So, is there a possibility that every user may have more than one main photo? If yes, please clarify! | |
| Oct 14, 2015 at 2:57 | comment | added | Coder Absolute | I will find a time to post much simpler answer. | |
| Oct 13, 2015 at 18:00 | comment | added | Jim | @CoderAbsolute I really appreciate the time you put into your answer but a_horse_with_no_name is right in that this is all "greek" to me. I don't know SQL Server. All I'm interested in is tables and pk/fk relationships. I particularly don't understand the User/Photo relationship. Your FK constraint seems to suggest there's a one-to-many relationship from photos to users when it's the other way around; one user can have many photos, not one photo belongs to many users. Again, I appreciate your answer, I just don't understand it. | |
| Oct 13, 2015 at 7:25 | history | edited | Coder Absolute | CC BY-SA 3.0 |
Corrected the typo!
|
| Oct 13, 2015 at 7:22 | comment | added | Coder Absolute | Sorry, my focus was purely on design! | |
| Oct 13, 2015 at 7:05 | comment | added | user1822 |
As the question is for Postgres, you should get rid of all the non-standard SQL syntax e.g. the [ for the identifiers and the physical properties (with .., clustered etc) for the table definitions.
|
|
| Oct 13, 2015 at 6:46 | review | First posts | |||
| Oct 13, 2015 at 6:48 | |||||
| Oct 13, 2015 at 6:42 | comment | added | Coder Absolute | I think the design is quite self-explanatory, but if you have questions then please ask! | |
| Oct 13, 2015 at 6:41 | history | answered | Coder Absolute | CC BY-SA 3.0 |