StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3368620
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-07-30T03:56:49.423
FavoriteCount
0
LastActivityDate
2010-07-30T03:56:49.423
LastEditDate
LastEditorUserId
0
OwnerUserId
36305
ParentId
3367920
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
This transformation: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:strip-space elements="*"/> <xsl:key name="kBooksByCat" match="books" use="@category = 'Z'"/> <xsl:template match="node()|@*" name="identity"> <xsl:copy> <xsl:apply-templates select="node()|@*"/> </xsl:copy> </xsl:template> <xsl:template match="/*"> <xml> <xsl:variable name="vNonZ" select="key('kBooksByCat', 'false')"/> <xsl:variable name="vCatZ" select="key('kBooksByCat', 'true')"/> <xsl:if test="$vNonZ"> <books category="A" count="{sum($vNonZ/@count)}"> <xsl:apply-templates select="$vNonZ/node()"/> </books> </xsl:if> <xsl:if test="$vCatZ"> <books category="B" count="{sum($vCatZ/@count)}"> <xsl:apply-templates select="$vCatZ/node()"/> </books> </xsl:if> </xml> </xsl:template> </xsl:stylesheet> </code></pre> when applied on the provided XML document: <pre><code><xml> <books category="X" count="2"> <book name="bookx1"/> <book name="bookx2"/> </books> <books category="Y" count="3"> <book name="booky1"/> <book name="booky2"/> <book name="booky3"/> </books> <books category="Z" count="2"> <book name="bookz1"/> <book name="bookz2"/> </books> </xml> </code></pre> produces the wanted, correct result: <pre><code><xml> <books category="A" count="5"> <book name="bookx1"/> <book name="bookx2"/> <book name="booky1"/> <book name="booky2"/> <book name="booky3"/> </books> <books category="B" count="2"> <book name="bookz1"/> <book name="bookz2"/> </books> </xml> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POneed to merge xml nodes based on an attribute value
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDimitre Novatchev
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POneed to merge xml nodes based on an attribute value
 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. COWow, awesome! that's exactly what I needed. Thank you so much
 singulars
 PostPostId
 PO
 UserUserId
 USgangt
2. CO@gangt: Glad my answer was useful. In SO gratitude is expressed by accepting the correct answer and/or upvoting useful answers.
 singulars
 PostPostId
 PO
 UserUserId
 USDimitre Novatchev

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.