StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4219096
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-18T20:11:36.023
FavoriteCount
0
LastActivityDate
2010-11-18T20:11:36.023
LastEditDate
LastEditorUserId
0
OwnerUserId
512657
ParentId
4206523
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
IfArchiveType is fine if you know you're only going to be doing one test. With a meta description, on the other hand, there's a good chance you'll want to do something different on category pages, say. While you could just pile up individual IfArchiveType tests for each, you'd do better to familiarize yourself with the <a href="http://www.movabletype.org/documentation/designer/archive-template-variables.html" rel="nofollow">archive template variables</a>(which provide a lot more besides) and use the generalized If/Else|If tags: <pre><code><mt:if name="entry_archive"> <meta name="description" content="[Entry archive-specific description]" /> <mt:elseif name="category_archive"> <meta name="description" content="[Category archive-specific description]" /> <mt:else> <meta name="description" content="[Site-wide fallback description]" /> </mt:if> </code></pre> ...which can then be further cleaned up using the Var tag: <pre><code><mt:if name="entry_archive"> <$mt:var name="metaDesc" value="[Entry archive-specific description]"$> <mt:elseif name="category_archive"> <$mt:var name="metaDesc" value="[Category archive-specific description]"$> <mt:else> <$mt:var name="metaDesc" value="[Site-wide fallback description]"$> </mt:if> <meta name="description" content="<$mt:var name="metaDesc"$>" /> </code></pre> [For clarity, I've omitted the modifiers Mike added, but they are a good idea to include.]
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMovable Type 4: IF / Else logic "if Entry"
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSu'
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMovable Type 4: IF / Else logic "if Entry"
 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
 VTAcceptedByOriginator
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.