StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17614292
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-12T11:49:46.530
FavoriteCount
0
LastActivityDate
2013-07-12T11:49:46.530
LastEditDate
LastEditorUserId
0
OwnerUserId
1718687
ParentId
17557134
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I would like to preface this answer with the disclaimer that I would not suggest using this solution on a regular basis. It is not the ideal way I would get this to work - but from a technical standpoint - for my particular situation - it should work out just fine. Ideally I would really like to have a TableB_ID field in the TableA table. That would then be an appropriate foreign key to the TableB table - and everything would work out great. That being said. Because the TableA_ID field on the TableB table is unique and not null - and - because you are able to specifically tell EF what to use as the primary key and foreign key - I was able to lie to EF and make it use for TableB the TableA_ID field as the primary key. Because of this - I was then able to tell TableA that its TableA_ID field was a foreign key to my TableB reference and all worked fine. Here is the fluent API bits I used to tell EF this lie. In my TableB EntityTypeConfiguration that I instantiate in the OnModelCreating override I say the following. <pre><code>this.HasKey(t => t.TableA_ID); this.HasRequired(b => b.TableA).WithOptional(a => a.TableB); </code></pre> This puts in the necessary bits to make everything point correctly for my situation. TableB ends up having a required link to TableA through the TableA_ID columns -and TableA has an optional link to TableB also through the TableA_ID columns. And, of course, since I have lied to EF and specifically told it that the TableA_ID field of TableB is the primary key - TableB_ID of the TableB table is not marked as such.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCode First to existing database - setting up a one to one relationship where TableA doesn't have an approprite foreign key reference to TableB
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSean Hosey
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCode First to existing database - setting up a one to one relationship where TableA doesn't have an approprite foreign key reference to TableB
 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
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.