StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2280140
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2010-02-17T11:22:55.833
FavoriteCount
0
LastActivityDate
2010-02-17T11:22:55.833
LastEditDate
LastEditorUserId
0
OwnerUserId
18771
ParentId
2276202
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I can think of two ways to do this. 1) identity template, hard coded author name: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select="node()|@*" /> </xsl:copy> </xsl:template>  <xsl:template match="notepad" />  <xsl:template match="notepad[author='John Doe']"> <xsl:copy-of select="." /> </xsl:template> </xsl:stylesheet> </code></pre> 2) modified identity template, XSL key, parameterized author name: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > <xsl:param name="theAuthor" select="'John Doe'" /> <xsl:key name="kNotepad" match="notepad[author]" use="concat(generate-id(..), '|', author)" /> <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select=" node()[not(self::notepad)] |key('kNotepad', concat(generate-id(), '|', $theAuthor)) |@*" /> </xsl:copy> </xsl:template> </xsl:stylesheet> </code></pre> The second approach requires a little explanation: <ul> <li>the <code><xsl:key></code> indexes all <code><nodepad></code> nodes that have an <code><author></code> by their parent's unique ID and the author name</li> <li>let's say the unique ID of <code><notepads></code> is <code>'id0815'</code>, then the key to the <code><notepad></code>s you are interested in would be <code>'id0815|Jon Doe'</code></li> <li>the identity template copies every node that is passed through it. It is modified in a way that it does not pass every node it finds through itself, but rather only: <ul> <li>any node that is not a <code><notepad></code>: <code>node()[not(self::notepad)]</code></li> <li>any attribute: <code>@*</code></li> <li>any node that is returned by the key.</li> </ul></li> <li>the call to <code>key()</code> naturally only ever returns anything at all on <code><notepads></code> elements (because it contains their unique ID)</li> <li>so when the template is currently processing a <code><notepads></code> element (<code>'id0815'</code> in our case), <code>key()</code> will return its <code>'Jon Doe'</code> children only, in all other cases it will turn up empty</li> <li>in contrast to solution 1) this one can be fed with a parameter, changing its behavior without changing its code</li> <li>it is worth noting that everything stays in input document order</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMore performant XSLT -- Selective Inclusion in Output
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTomalak
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMore performant XSLT -- Selective Inclusion in Output
 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
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.