StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
840182
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
10
CommunityOwnedDate
CreationDate
2009-05-08T14:52:37.387
FavoriteCount
0
LastActivityDate
2017-02-08T22:56:14.210
LastEditDate
2017-02-08T22:56:14.210
LastEditorUserId
732792
OwnerUserId
55159
ParentId
840162
PostTypeId
2
Score
259
ViewCount
0
LastEditorDisplayName
text
Body
Short answer: yes. Long answer: <ul> <li>You need your table to be joinable on something</li> <li>If you want your table to be clustered, you need some kind of a primary key.</li> <li>If your table design does not need a primary key, rethink your design: most probably, you are missing something. Why keep identical records?</li> </ul> In MySQL, the InnoDB storage engine always creates a primary key if you didn't specify it explicitly, thus making an extra column you don't have access to. Note that a primary key can be composite. If you have a many-to-many link table, you create the primary key on all fields involved in the link. Thus you ensure that you don't have two or more records describing one link. Besides the logical consistency issues, most RDBMS engines will benefit from including these fields in a unique index. And since any primary key involves creating a unique index, you should declare it and get both logical consistency and performance. See this article in my blog for why you should always create a unique index on unique data: <ul> <li><a href="http://explainextended.com/2009/04/23/making-an-index-unique/" rel="noreferrer">Making an index UNIQUE</a></li> </ul> P.S. There are some very, very special cases where you don't need a primary key. Mostly they include log tables which don't have any indexes for performance reasons.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POShould each and every table have a primary key?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRandy Marsh
UserOwnerUserId
1. USQuassnoi
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POShould each and every table have a primary key?
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.