StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17280135
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-06-24T16:14:00.893
FavoriteCount
0
LastActivityDate
2013-06-24T18:03:54.867
LastEditDate
2013-06-24T18:03:54.867
LastEditorUserId
252228
OwnerUserId
252228
ParentId
17277879
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
If I understand your requirement correctly then <code>@country</code> always exists so we can do a key based lookup on that attribute. For the other two attributes <code>@areacode</code> and <code>@division</code> you want take the <code>code</code> which has both attributes matching with priority over a <code>code</code> which has one matching attribute with priority over a <code>code</code> with no matching attribute. So I would simply create a sequence of the different priorities and take first one found: <pre><code><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:param name="lkp-url" select="'test2013062402.xml'"/> <xsl:variable name="lkp-doc" select="doc($lkp-url)"/> <xsl:key name="by-country" match="code" use="@country"/> <xsl:param name="c" select="'ca'"/> <xsl:param name="ac" select="'222'"/> <xsl:param name="d" select="'46'"/> <xsl:template match="/"> <xsl:value-of select="(key('by-country', $c, $lkp-doc)[@areacode = $ac and @division = $d], key('by-country', $c, $lkp-doc)[not(@areacode) and @division = $d], key('by-country', $c, $lkp-doc)[@areacode = $ac and not(@division)], key('by-country', $c, $lkp-doc)[not(@areacode) and not(@division)])[1]/@id"/> </xsl:template> </xsl:stylesheet> </code></pre> I don't know which of the two attributes has priority, you might want to shuffle the second and third item in the sequence I created in the code if <code>areacode</code> has priority. The above code should be shortened to <pre><code><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:param name="lkp-url" select="'test2013062402.xml'"/> <xsl:variable name="lkp-doc" select="doc($lkp-url)"/> <xsl:key name="by-country" match="code" use="@country"/> <xsl:param name="c" select="'ca'"/> <xsl:param name="ac" select="'222'"/> <xsl:param name="d" select="'46'"/> <xsl:template match="/"> <xsl:variable name="cs" select="key('by-country', $c, $lkp-doc)"/> <xsl:value-of select="($cs[@areacode = $ac and @division = $d], $cs[not(@areacode) and @division = $d], $cs[@areacode = $ac and not(@division)], $cs[not(@areacode) and not(@division)])[1]/@id"/> </xsl:template> </xsl:stylesheet> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXml lookup tables
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMartin Honnen
UserOwnerUserId
1. USMartin Honnen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POXml lookup tables
 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
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
 VTUpMod
CommentsPostId
1. COThanks for the response. Based on testing against my real life scenario it works beautifully. I'll be adding this to my personal XSL tips Wiki!
 singulars
 PostPostId
 PO
 UserUserId
 USGavin

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.