StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20239096
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-27T09:55:31.460
FavoriteCount
0
LastActivityDate
2013-11-27T09:55:31.460
LastEditDate
LastEditorUserId
0
OwnerUserId
1987598
ParentId
20232916
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
This is an extension to the answer given by @Lego Stormtroopr. He suggests starting with two templates each matching one type: <pre><code><xsl:template match="/data[admin/type='one']/detail">  </xsl:template> <xsl:template match="/data[admin/type='two']/detail">  </xsl:template> </code></pre> Now for the <code>content to appear for ALL types</code>, here are two possibilities. If the part appearing for all types is about content, use a global variable and store it there: <pre><code><xsl:variable name="var1">  </xsl:variable> <xsl:template match="/data[admin/type='one']/detail">  <xsl:value-of select="$var1"/>  </xsl:template> <xsl:template match="/data[admin/type='two']/detail">  <xsl:value-of select="$var1"/>  </xsl:template> </code></pre> If there are input elements inside <code>detail</code> that you need to catch, just define another template for them and let <code>apply-templates</code> find them. <pre><code><xsl:template match="/data[admin/type='one']/detail">  <xsl:apply-templates/>  </xsl:template> <xsl:template match="/data[admin/type='two']/detail">  <xsl:apply-templates/>  </xsl:template> <xsl:template match="*[parent::detail]">  </xsl:template> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBest way to have two XSLT templates apply to same element
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMathias Müller
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.