StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14958022
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-19T12:53:35.593
FavoriteCount
0
LastActivityDate
2013-02-19T13:17:56.867
LastEditDate
2013-02-19T13:17:56.867
LastEditorUserId
2054185
OwnerUserId
2054185
ParentId
14956844
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The following code do what you try to achieve. However, depending on how the data set can change maybe is not he most efficient approach. I am assuming that YColumns can appear in a different order and that we can find any number of datasets (not just 2) in the source file. If some of those restrictions can be removed, the solution could be simpler. <pre><code><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output method="xml" indent="yes" />  <xsl:param name="category" select="'Country'" />  <xsl:template match="Data"> <data> <xsl:apply-templates select="*" /> </data> </xsl:template> <xsl:template match="Rows">  <categories> <xsl:apply-templates select="Row/XColumns[Name = $category]" /> </categories>  <xsl:apply-templates select="Row[1]/YColumns" /> </xsl:template>  <xsl:template match="XColumns"> <category label="{Value}" /> </xsl:template>  <xsl:template match="YColumns"> <xsl:variable name="name" select="Name" /> <dataset seriesName="{$name}"> <xsl:for-each select="../../Row/YColumns[Name = $name]/Value"> <set value="{.}" /> </xsl:for-each> </dataset> </xsl:template> </xsl:stylesheet> </code></pre> UPDATE: a more efficient approach is using <xsl:key> to index all YColumn names. So you have to add <pre><code><xsl:key name="data-set" match="YColumns/Value" use="../Name" /> </code></pre> as a direct child of <xsl:stylesheet> And change the expression following expression <pre><code>../../Row/YColumns[Name = $name]/Value </code></pre> to <pre><code>key('data-set', $name) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to select node/value based on given value in xslt?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPablo Pozo
UserOwnerUserId
1. USPablo Pozo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to select node/value based on given value in 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
 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.