StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhat Db structure should I use with 2 the same comment tables for 2 different parent tables
primarykey
Id
4119246
data
AcceptedAnswerId
4119307
AnswerCount
5
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-07T19:19:56.187
FavoriteCount
0
LastActivityDate
2010-11-10T22:55:20.613
LastEditDate
2010-11-07T19:24:08.807
LastEditorUserId
85616
OwnerUserId
255920
ParentId
0
PostTypeId
1
Score
3
ViewCount
165
LastEditorDisplayName
text
Body
This is a tough design question for a application I'm working on. I have 2 different items in my app that both will use comments. What but I can't decide how to design my database. There are 2 possibilities here. The first is a different comment table for every table that needs comments (normalized way): <pre><code>movies -> movie_comments articles -> article_comments </code></pre> The second way I was thinking of was the use of a generic comments table and then have a many 2 many relationship for the comment and movie|article relations. Eg <pre><code>comments comments_movies (movie_id, comment_id) comments_articles (article_id, comment_id) </code></pre> What is your opinion on that the best method would be and can you give a good reason so I can decide.
Tags
<mysql><database-design>
Title
What Db structure should I use with 2 the same comment tables for 2 different parent tables
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USThe Pixel Developer
UserOwnerUserId
1. USRJD22
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POWhat Db structure should I use with 2 the same comment tables for 2 different parent tables
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWhat Db structure should I use with 2 the same comment tables for 2 different parent tables
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POWhat Db structure should I use with 2 the same comment tables for 2 different parent tables
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.