StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1297292
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-08-19T00:33:23.097
FavoriteCount
0
LastActivityDate
2018-06-07T07:39:13.043
LastEditDate
2018-06-07T07:39:13.043
LastEditorUserId
87861
OwnerUserId
87861
ParentId
1297272
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
The following email address is only 94 characters: i.have.a.really.long.name.like.seetharam.krishnapillai@AReallyLongCompanyNameOfSomeKind.com.au <ul> <li>Would an organisation actually give you an email that long?</li> <li>If they were stupid enough to, would you actually use an email address like that? </li> <li>Would anyone? Of course not. Too long to type and too hard to remember.</li> </ul> Even a 92-year-old technophobe would figure out how to sign up for a nice short gmail address, and just use that, rather than type this into your registration page. Disk space probably isn't an issue, but there are at least two problems with allowing user input fields to be many times longer than they need to be: <ul> <li>Displaying them could mess up your UI (at best they will be cut off, at worst they push your containers and margins around) </li> <li>Malicious users can do things with them you can't anticipate (like those cases where hackers used a free online API to store a bunch of data) </li> </ul> I like 50 chars: 123456789.123456789.123456789@1234567890123456.com If one user in a million has to use their other email address to use my app, so be it. (Statistics show that no-one actually enters more than about 40 chars for email address, see e.g.: ZZ Coder's answer <a href="https://stackoverflow.com/a/1297352/87861">https://stackoverflow.com/a/1297352/87861</a>)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow long should SQL email fields be?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMGOwen
UserOwnerUserId
1. USMGOwen
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
 VTDownMod
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
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.