StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7650437
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-04T15:38:34.830
FavoriteCount
0
LastActivityDate
2011-10-04T17:36:08.987
LastEditDate
2011-10-04T17:36:08.987
LastEditorUserId
977267
OwnerUserId
977267
ParentId
7639652
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
FINAL SOLUTION Thanks to your reference to InverseProperty I found an amazing article that covers exactly what I wanted to accomplish using fluent API. This article was written in January, but I'm pretty sure CTP5 is now officially part of the MVC 3 and EF core. <a href="http://weblogs.asp.net/manavi/archive/2011/01/23/associations-in-ef-code-first-ctp5-part-3-one-to-one-foreign-key-associations.aspx" rel="nofollow">Associations in EF Code First CTP5</a> Okay...I'm going to document what I found to work great! I hate it when people leave partial answers, so here we go. There is a little redundancy here, but it works. My Quote Class looks like this: <pre><code> [ForeignKey("Creator")] public virtual int CreatorID { get; set; } [InverseProperty("CreatedQuotes")] public virtual User Creator { get; set; } [ForeignKey("Agent")] public virtual int AgentID { get; set; } [InverseProperty("OwnedQuotes")] public virtual User Agent { get; set; } [ForeignKey("Manager")] public virtual int ManagerID { get; set; } [InverseProperty("ManagedQuotes")] public virtual User Manager { get; set; } </code></pre> Then my User class looks like this: <pre><code> public virtual ICollection<Quote> CreatedQuotes { get; set; } public virtual ICollection<Quote> OwnedQuotes { get; set; } public virtual ICollection<Quote> ManagedQuotes { get; set; } </code></pre> Finally, my DBContext class looks like this: <pre><code> protected override void OnModelCreating(DbModelBuilder modelBuilder) { modelBuilder.Conventions.Remove<PluralizingTableNameConvention>(); modelBuilder.Entity<Quote>() .HasRequired(a => a.Manager) .WithMany() .HasForeignKey(u => u.ManagerID); modelBuilder.Entity<Quote>() .HasRequired(a => a.Agent) .WithMany() .HasForeignKey(u => u.AgentID).WillCascadeOnDelete(false); modelBuilder.Entity<Quote>() .HasRequired(a => a.Manager) .WithMany() .HasForeignKey(u => u.ManagerID).WillCascadeOnDelete(false); } </code></pre> You can see the redundancy in the ForeignKey annotation in the Quote class and the Fluent API mapping in the DbContext class, but it's not hurting anything. I could probably do away with the annotations in the Quote class, but the Fluent API is necessary to set the cascading rule to false to prevent foreign key conflicts. I have been able to navigate both directions with no problems and exactly as expected. Thanks for all your help!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUse MVC 3 and Entity Framework, how do I map a different instance of the same class to 3 different collection properties?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USWatermark Studios
UserOwnerUserId
1. USWatermark Studios
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUse MVC 3 and Entity Framework, how do I map a different instance of the same class to 3 different collection properties?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 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.