StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POEntity Framework 4.1 - Segregating an entity into multiple tables (Code-First)
primarykey
Id
9248925
data
AcceptedAnswerId
9249052
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-12T12:52:21.197
FavoriteCount
0
LastActivityDate
2012-02-12T13:11:55.447
LastEditDate
LastEditorUserId
0
OwnerUserId
1205051
ParentId
0
PostTypeId
1
Score
1
ViewCount
167
LastEditorDisplayName
text
Body
I'm trying to find out how I can re-use a simple 'Comment' entity type for multiple scenarios where something is 'commentable' in my application. At the moment, I have a couple of entities that a user is able to post comments to. Examples include Blogs, Profiles and Photos - these can all be 'commented' on. I'd like to be able to use the same 'Comment' class for each of these scenarios, but I don't want to end up with one HUGE table full of comments for everything. I figure it would be much more efficient to at least store a table of BlogComments, PhotoComments, and ProfileComments. At the moment, my Comment class looks like this: <pre><code>public class Comment { [Key] public int Id { get; set; } public int ContextId { get; set; } [StringLength(256)] public string Content { get; set; } public DateTime DatePosted { get; set; } public virtual Member Author { get; set; } } </code></pre> Presumably, I'd need the 'ContextId' field to refer to the particular thing being commented on. This Id might be the Id of a Blog, a Profile or a Photo. I was hoping to be able to refer to comments much like a normal ICollection in these classes, and I have some code like this for the Photos as an example: <pre><code>public class Photo { [Key] public int Id { get; set; } [StringLength(48)] public string FileName { get; set; } public virtual Member Owner { get; set; } public virtual ICollection<Comment> Comments { get; set; } } </code></pre> I've been pointed to various articles during my searches, but none really seem relevant to my particular situation. How can I map these comment collections to different tables, and avoid having a comment "super-table"? Any help, pointers or advice would be hugely appreciated :)
Tags
<asp.net-mvc-3><ef-code-first>
Title
Entity Framework 4.1 - Segregating an entity into multiple tables (Code-First)
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAlex
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
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POEntity Framework 4.1 - Segregating an entity into multiple tables (Code-First)
 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.