StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17929867
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-07-29T17:00:14.077
FavoriteCount
0
LastActivityDate
2013-07-29T17:00:14.077
LastEditDate
LastEditorUserId
0
OwnerUserId
270591
ParentId
17926413
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
It's not possible to customize the foreign key constraint name with data annotations or <code>DbModelBuilder</code> Fluent API. However, you can control the name with code-based migrations. <ul> <li>First option: When the tables get created via migrations: The migration code that gets automatically generated for the join table would look like this: <pre><code>public partial class MyMigration : DbMigration { public override void Up() { CreateTable("GroupUser", c => new { UserId = c.Int(nullable: false), GroupId = c.Int(nullable: false), }) .PrimaryKey(t => new { t.UserId, t.GroupId }) .ForeignKey("User", t => t.UserId, cascadeDelete: true) .ForeignKey("Group", t => t.GroupId, cascadeDelete: true) .Index(t => t.UserId) .Index(t => t.GroupId); // ... } } </code></pre> Here you can modify the two <code>ForeignKey</code> method calls to set a custom constraint name before you call <code>update-database</code>: <pre><code> .ForeignKey("User", t => t.UserId, cascadeDelete: true, name: "FK_GroupUser_UserId") .ForeignKey("Group", t => t.GroupId, cascadeDelete: true, name: "FK_GroupUser_GroupId") </code></pre></li> <li>Second option: When the tables already exist you can drop the constraint and add a new renamed one in a migration: <pre><code>public partial class MyMigration : DbMigration { public override void Up() { DropForeignKey("UserGroup", "UserId", "User"); DropForeignKey("UserGroup", "GroupId", "Group"); AddForeignKey("UserGroup", "UserId", "User", name: "FK_GroupUser_UserId"); AddForeignKey("UserGroup", "GroupId", "Group", name: "FK_GroupUser_GroupId") // ... } } </code></pre></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEF code first - custom foreign key constraint name
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSlauma
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POEF code first - custom foreign key constraint name
 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.