StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6887630
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2011-07-31T05:03:17.333
FavoriteCount
0
LastActivityDate
2011-08-01T04:17:03.080
LastEditDate
2011-08-01T04:17:03.080
LastEditorUserId
36305
OwnerUserId
36305
ParentId
6876293
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Here is an efficient and short solution, using keys <a href="http://www.jenitennison.com/xslt/grouping/muenchian.html" rel="nofollow">(Muenchian grouping</a>): <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="kDocById" match="document" use="@refid"/> <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select="node()|@*"/> </xsl:copy> </xsl:template> <xsl:template match="group"> <xsl:copy> <xsl:apply-templates select= "@* | node()[not(self::document)] | document [generate-id() = generate-id(key('kDocById', @refid)[1]) ]"/> </xsl:copy> </xsl:template> </xsl:stylesheet> </code></pre> when this transformation is applied on the provided XML document (reflecting the latest refinement made in a comment by the OP): <pre><code><data> <group id= "1"> <phrase>Doc1</phrase> <document refid ="3"/> <document refid ="5"/> <document refid= "1"/> </group> <group id= "2"> <phrase>Doc2</phrase> <document refid ="2"/> <document refid ="3"/> <document refid= "6"/> </group> <group id= "3"> <phrase>Doc3</phrase> <document refid ="2"/> <document refid ="3"/> <document refid= "4"/> </group> </data> </code></pre> the wanted, correct result is produced: <pre><code><data> <group id="1"> <phrase>Doc1</phrase> <document refid="3"/> <document refid="5"/> <document refid="1"/> </group> <group id="2"> <phrase>Doc2</phrase> <document refid="2"/> <document refid="6"/> </group> <group id="3"> <phrase>Doc3</phrase> <document refid="4"/> </group> </data> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIf a number repeats, only show it once
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDimitre Novatchev
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. POIf a number repeats, only show it once
 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
 VTAcceptedByOriginator
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.