StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2913565
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
11
CommunityOwnedDate
CreationDate
2010-05-26T13:53:21.577
FavoriteCount
0
LastActivityDate
2010-05-26T15:41:50.997
LastEditDate
2010-05-26T15:41:50.997
LastEditorUserId
54283
OwnerUserId
54283
ParentId
2913530
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
Use templates to define behavior on specific elements <pre><code> <xsl:template match="description"> <xsl:element name="newprice"> <xsl:apply-templates/> </xsl:element> </xsl:template> <xsl:template match="p"> <xsl:apply-templates/> </xsl:template> </code></pre> The first template says to swap <code>description</code> with <code>newprice</code>. The second one says to ignore the <code>p</code> element. If you're unfamiliar with the identity template, <a href="http://www.xmlplease.com/xsltidentity" rel="nofollow noreferrer">take a look here</a> for a few examples. EDIT: Given the new example, we can see that you want to only extract the description element and its contents. Notice that the template action starts with the <code>match="/"</code> template. We can use this control where our stylesheet starts and thus skip much of the riffraff we want to filter out. change the <code><xsl:template match="/"></code> to something more like: <pre><code> <xsl:template match="/"> <xsl:apply-templates select="//description"/>  </xsl:template> </code></pre> So altogether our solution looks like this: <pre><code><xsl:stylesheet xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0" exclude-result-prefixes="xs"> <xsl:template match="/"> <xsl:apply-templates select="//description" /> </xsl:template>  <xsl:template match="@*|node()"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> <xsl:template match="description"> <xsl:element name="newprice"> <xsl:apply-templates/> </xsl:element> </xsl:template> <xsl:template match="p"> <xsl:apply-templates/> </xsl:template> </xsl:stylesheet> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPreserve certain html tags during XSLT
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJon W
UserOwnerUserId
1. USJon W
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPreserve certain html tags during XSLT
 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
 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

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.