StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10449517
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-05-04T13:11:22.733
FavoriteCount
0
LastActivityDate
2012-05-05T05:44:23
LastEditDate
2012-05-05T05:44:23
LastEditorUserId
36305
OwnerUserId
36305
ParentId
10442273
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I would use keys -- both for convenience and efficiency: <pre><code>key('kPlaysByAuthor', 'Shakespeare, William') </code></pre> To select just the <code>playcode</code>: <pre><code>key('kPlaysByAuthor', 'Shakespeare, William')/playcode </code></pre> Here is a complete example: <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="kPlaysByAuthor" match="edition" use="metadataBlock/meta[@name='Creator']/@content"/> <xsl:template match="/"> <xsl:copy-of select= "key('kPlaysByAuthor', 'Shakespeare, William')/playcode"/> </xsl:template> </xsl:stylesheet> </code></pre> when this transformation is applied on the following XML document: <pre><code><works> <editions> <edition> <playtitle>Henry IV, Part 1</playtitle> <playcode>1H4</playcode> <genre>play</genre> <metadataBlock> <meta content="Shakespeare, William" name="Creator"/> </metadataBlock> </edition> <edition> <playtitle>Some Title</playtitle> <playcode>XYZ</playcode> <genre>play</genre> <metadataBlock> <meta content="Someone, Else" name="Creator"/> </metadataBlock> </edition> </editions> </works> </code></pre> the wanted, correct result is produced: <pre><code><playcode>1H4</playcode> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXPath with multiple predicates
 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. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.