StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4908541
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-02-05T17:57:30.543
FavoriteCount
0
LastActivityDate
2011-02-05T18:02:56.580
LastEditDate
2011-02-05T18:02:56.580
LastEditorUserId
36305
OwnerUserId
36305
ParentId
4908274
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
This transformation produces the unique team ids even if their values belonged to any number of differently named attributes: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:my="my:my" exclude-result-prefixes="my"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:key name="kTeamById" match="@*[name()=document('')/*/my:teamIdNames/*]" use="."/> <my:teamIdNames> <name>HomeTeamId</name> <name>AwayTeamId</name> </my:teamIdNames> <xsl:variable name="vAttrNames" select= "document('')/*/my:teamIdNames/*"/> <xsl:template match="/"> <xsl:apply-templates select= "//Fixture/@*[name()=$vAttrNames]"/> </xsl:template> <xsl:template match= "@*[name()=document('')/*/my:teamIdNames/*] [generate-id() = generate-id(key('kTeamById', .)[1]) ] "> <xsl:value-of select="."/> </xsl:template> </xsl:stylesheet> </code></pre> when this transformation is applied on the provided XML document: <pre><code><League> <Week Date="26/04/2010 19:00"> <Fixture Id="542" HomeTeamId="371" HomeTeam="London Raiders Green" AwayTeamId="13" AwayTeam="Richmond Swingers"/> <Fixture Id="543" HomeTeamId="45" HomeTeam="Spartans" AwayTeamId="15" AwayTeam="Panthers"/> <Fixture Id="544" HomeTeamId="370" HomeTeam="Fat Cats" AwayTeamId="381" AwayTeam="London Raiders Orange" /> </Week> <Week Date="27/04/2010 19:00"> <Fixture Id="548" HomeTeamId="3" HomeTeam="The Mob" AwayTeamId="81" AwayTeam="London Raiders Red"/> <Fixture Id="549" HomeTeamId="373" HomeTeam="Intellect" AwayTeamId="83" AwayTeam="Tornadoes"/> </Week> </League> </code></pre> the wanted result is produced: <pre><code>371 13 45 15 370 381 3 81 373 83 </code></pre> Do note: This solution doesn't assume that the sources of the ids for the teams come just from the attributes named <code>HomeTeamId</code> and <code>AwayTeamId</code>. In fact, any variable set of names can be used (and included in a separate document), so this is a very powerful, generic solution.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSelecting the unique values from multiple attributes in an XML document using XSLT 1.0
 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. This table or related slice is empty.
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
CommentsPostId
1. CO+1 Because this answers the question's title much better, besides the OP original problem.
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
2. COWow, that is indeed a very powerful generic solution. Thanks. I've +1ed because of that as well, even though I have used Martin's solution because I think that I'll have a better chance of remembering how his works when I come back and have to look at it years later! :)
 singulars
 PostPostId
 PO
 UserUserId
 USMajorRefactoring

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.