StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1497940
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-09-30T12:59:16.513
FavoriteCount
0
LastActivityDate
2009-09-30T13:06:08.867
LastEditDate
2009-09-30T13:06:08.867
LastEditorUserId
18771
OwnerUserId
18771
ParentId
1496434
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
This solution does what you want: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" encoding="utf-8" omit-xml-declaration="yes" /> <xsl:template match="/"> <root> <xsl:attribute name="path"> <xsl:apply-templates select="(//@title)[1]" mode="make-path" /> </xsl:attribute> </root> </xsl:template> <xsl:template match="*|@*" mode="make-path"> <xsl:apply-templates select="parent::*" mode="make-path" /> <xsl:text>/</xsl:text> <xsl:apply-templates select="." mode="make-name" /> <xsl:choose> <xsl:when test="self::section"> <xsl:apply-templates select="@id" mode="make-predicate" /> </xsl:when> <xsl:when test="self::subPage"> <xsl:apply-templates select="@user" mode="make-predicate" /> </xsl:when> </xsl:choose> </xsl:template> <xsl:template match="*|@*" mode="make-predicate"> <xsl:text>[</xsl:text> <xsl:apply-templates select="." mode="make-name" /> <xsl:text> = '</xsl:text> <xsl:value-of select="." /> <xsl:text>']</xsl:text> </xsl:template> <xsl:template match="*" mode="make-name"> <xsl:value-of select="name()" /> </xsl:template> <xsl:template match="@*" mode="make-name"> <xsl:text>@</xsl:text> <xsl:value-of select="name()" /> </xsl:template> </xsl:stylesheet> </code></pre> When applied to <pre><code><section id="someId"> <page> <subPage user="UserA" title="test" /> <subPage user="UserB" title="blah" /> </page> <page> <subPage user="UserC" title="fooh" /> </page> </section> </code></pre> you get: <pre><code><root path="/section[@id = 'someId']/page/subPage[@user = 'UserA']/@title" /> </code></pre> The <code><xsl:choose></code> is the configurable spot (add as many <code><xsl:when></code>s as you like): <pre><code> <xsl:when test="self::section">  <xsl:apply-templates select="@id" mode="make-predicate" /> </xsl:when> </code></pre> also possible: <pre><code><xsl:when test="self::section"> <xsl:apply-templates select="@name|@category|subElement" mode="make-predicate" /> </xsl:when> </code></pre> which would lead to <pre><code><root path="/section[@name = 'someName'][@category = 'somecat'][subElement = 'xyz']/..." /> </code></pre> The only issue I see is with predicate values that contain single quotes. They would break the XPath.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGetting XSLT Current Node, formatted as XPath Query?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTomalak
UserOwnerUserId
1. USTomalak
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGetting XSLT Current Node, formatted as XPath Query?
 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. CONice use of mode
 singulars
 PostPostId
 PO
 UserUserId
 USTeun D
2. COHardcore man, thanks for this.
 singulars
 PostPostId
 PO
 UserUserId
 USLance Pollard

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.