StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5647680
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-04-13T10:27:30.700
FavoriteCount
0
LastActivityDate
2011-04-13T10:46:48.777
LastEditDate
2011-04-13T10:46:48.777
LastEditorUserId
26414
OwnerUserId
26414
ParentId
5647650
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
The short answer is no - don't put "FK" in column names of foreign key columns. You can still signal the intent of the column though, here's how I do it: <h2>Naming foreign key columns</h2> It depends on your naming convention for the target of the FK. If you have <code>Id</code>, then I'd prepend the table name when creating FK columns. Example 1: For table <code>User</code> with PK <code>Id</code> and table <code>Workitem</code> with user ID FK, I'd call the column <code>Workitem.UserId</code>. If there were more than one FK between the same tables, I'd make this clear in the column name: Example 2: For table <code>User</code> with PK <code>Id</code> and table <code>Workitem</code> with "assigned to user ID" and "created by user ID" FKs, I'd call the columns <code>Workitem.CreatedByUserId</code> and <code>Workitem.AssignedToUserId</code>. If your naming convention for PKs is more like <code>UserId</code>, then you'd factor that into the above examples so as not to end up with <code>UserUserId</code>. <h2>Naming foreign key constraints</h2> This is mine: <pre><code>FK_childtablename_[differentiator]parenttablename </code></pre> The differentiator is used when there is more than one FK between the same two tables (e.g. <code>CreatedByUserId</code> and <code>AssignedToUserId</code>). Often I use the child table's column name for this. Example 1: Given tables: <code>Workitem</code> and <code>User</code> Where <code>User</code> has <code>CreatedByUserId</code> and <code>AssignedToUserId</code> Foreign key names are <code>FK_Workitem_User_CreatedByUser</code> and <code>FK_Workitem_AssignedToUser</code> I use double-underscores if tables/columns have underscores in the name: Example 2: Given tables: <code>work_item</code> and <code>user</code> Where <code>user</code> has <code>created_by_user_id</code> and <code>assigned_to_user_id</code> Foreign key names are <code>FK_work_item__created_by_user</code> and <code>FK_work_item__assigned_to_user</code>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODatabase column naming for foreign key
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNeil Barnwell
UserOwnerUserId
1. USNeil Barnwell
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. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COYou have shown the FK _constraint_ name, not the column name :)
 singulars
 PostPostId
 PO
 UserUserId
 USOded
2. COOops, I'll update...
 singulars
 PostPostId
 PO
 UserUserId
 USNeil Barnwell

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.