StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
463912
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-01-21T02:19:17.607
FavoriteCount
0
LastActivityDate
2009-01-21T02:19:17.607
LastEditDate
LastEditorUserId
0
OwnerUserId
14263
ParentId
367426
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Divs and spans are kind like wildcard tags that have no semantic meaning. You can use them to group or identify elements when no other tag is appropriate (like tables, lists or headings). Their differences are: div <ul> <li>it's a block level element </li> <li>default display property is block which means: <ul> <li>its as wide as its container</li> <li>always makes line breaks before and after </li> </ul></li> <li>can contain other block level elements like <code>p</code>, <code>h1</code>, <code>table</code>, <code>ul</code>, <code>blockquote</code>, <code>div</code> </li> <li>can contain other inline elements like <code>img</code>, <code>strong</code>, <code>em</code>, <code>input</code>, <code>a</code>, <code>span</code></li> </ul> span <ul> <li>is an inline element </li> <li>default display property is inline which means: <ul> <li>is as narrow as its content </li> <li>does not makes any line break if not necessary) </li> <li>you can use the css property <code>vertical-align</code> with it</li> </ul></li> <li>cannot contain block level elements</li> <li>can contain other inline elements like <code>img</code>, <code>strong</code>, <code>em</code>, <code>input</code>, <code>a</code>, <code>span</code> </li> </ul> You can always change their default display property with css, but you cannot change the type of elements they can contain, regardless of the display property value. For instance: <pre><code> this will be displayed like a div, but still cannnot contain block level elements </code></pre> Because they are "generic" tags, they're usually used for <a href="http://microformats.org" rel="nofollow noreferrer">microformats</a> in conjunction with classes. For instance: <code>555-5555</code>, because there is no <code><tel></code> tag. As for the image wrapping, if the image is directly related to the text, you could use: <pre><code><img src="image.jpg" style="float: right" alt="my image" />Long paragraph. </code></pre> And no divs or spans would be required. However, if it is not, then you could use: <pre><code>unrelated to the image <div> <img src="image.jpg" style="float: right" alt="my image" /> Long paragraph. </div> </code></pre> Here <code>div</code> is necessary because <code>p</code> is a block level element. Finally, for more information you can check <a href="http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4" rel="nofollow noreferrer">the official W3C spec topic</a> about divs and spans.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFormatting inline items? What does the general code look like?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMarco Luglio
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. 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.