StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9818722
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-03-22T08:32:31.763
FavoriteCount
0
LastActivityDate
2012-03-22T17:08:24.783
LastEditDate
2012-03-22T17:08:24.783
LastEditorUserId
7585
OwnerUserId
7585
ParentId
9792382
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Another slightly different approach (although not necessarily a better approach) is to pass a parameter to each student match which contains a comma-delimited of group attributes that have already been output. Every time you match a student, you check whether their group is in his parameter, and if not output the student, and get the next one, appending the current group to the parameter. Here is the XSLT, which I have commented to try and explain things better <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output indent="yes"/> <xsl:template match="Socrates"> <Socrates> <xsl:apply-templates select="Student[1]"/> </Socrates> </xsl:template> <xsl:template match="Student">  <xsl:param name="groupList" select="','" /> <xsl:choose>  <xsl:when test="contains($groupList, concat(',', @group, ','))">  <xsl:apply-templates select="following-sibling::Student[1]"> <xsl:with-param name="groupList" select="$groupList" /> </xsl:apply-templates> </xsl:when>  <xsl:otherwise>  <xsl:copy-of select="." />  <xsl:apply-templates select="following-sibling::Student[@name!=current()/@name][1]"> <xsl:with-param name="groupList" select="concat($groupList, @group, ',')" /> </xsl:apply-templates> </xsl:otherwise> </xsl:choose> </xsl:template> </xsl:stylesheet> </code></pre> When applied to your sample XML, the following is output <pre><code><Socrates> <Student name="Aristotle" group="1" /> <Student name="Plato" group="2" /> <Student name="Xenophon" group="4" /> <Student name="Critias" group="3" /> </Socrates> </code></pre> Note that this does assume the student elements are always ordered by name in the input XML.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT Retrieving First Unique Value
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTim C
UserOwnerUserId
1. USTim C
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POXSLT Retrieving First Unique 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
 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. COThanks!! This surely looks right. I have not been able to test it yet. Does it works with XSLT 1.0?
 singulars
 PostPostId
 PO
 UserUserId
 USSumit Bhuttan
2. COThis is indeed an XSLT 1.0 solution.
 singulars
 PostPostId
 PO
 UserUserId
 USTim C

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.