StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4591081
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-01-04T06:05:01.967
FavoriteCount
0
LastActivityDate
2011-01-04T06:05:01.967
LastEditDate
LastEditorUserId
0
OwnerUserId
157247
ParentId
4591069
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
This is the perennial problem. The best you can do is: <ol> <li>Use a <code>DOCTYPE</code>. It doesn't much matter what <code>DOCTYPE</code> you use, but use one. This tells the browser to use its standards-compliant mode. (The degree to which it will actually be standards-compliant will vary, but it tells the browser to at least try.)</li> <li>Make sure your pages <a href="http://validation.w3.org" rel="nofollow">validate</a> according to that <code>DOCTYPE</code> (or at least mostly validate; if you're using an older <code>DOCTYPE</code> but need custom attributes, they won't validate).</li> <li>Decide which browsers you will support. I don't mean you're not shooting for complete compatibility, but you have limited resources (see next point). So find out what your target audience use, and draw a line somewhere. Net Applications and StatCounter have browser statistics pages <a href="http://marketshare.hitslink.com/browser-market-share.aspx?qprid=2" rel="nofollow">here</a> and <a href="http://gs.statcounter.com/" rel="nofollow">here</a>, and they likely represent different audiences; they may be a place to start, but of course the gold standard is your own logs.</li> <li>Test, test, test with your target browsers. Not at the end, when you have things all pretty in your preferred browser; throughout the development cycle so you don't go too far down a path and then find that that just won't work in something you need to support. </li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POmaintenance of website in different browsers
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UST.J. Crowder
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
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.