StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19718283
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-10-31T23:19:23.260
FavoriteCount
0
LastActivityDate
2013-10-31T23:42:45.850
LastEditDate
2017-05-23T12:08:50.383
LastEditorUserId
-1
OwnerUserId
0
ParentId
19718048
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
user764357
text
Body
Your XSLT is very <a href="http://www.ibm.com/developerworks/library/x-xdpshpul.html" rel="nofollow noreferrer">"pull" focused rather than "push"</a> focused and could use some re-engineering to be more functional (in the functional programming sense). But the main error is here: <pre><code> <xsl:template name="folder"> </code></pre> This is declaring a <a href="http://msdn.microsoft.com/en-us/library/ms256459%28v=vs.110%29.aspx" rel="nofollow noreferrer">"named template" but it's never called</a>. Not a bad thing, as <a href="https://stackoverflow.com/questions/4478045/what-are-the-difference-between-call-template-and-apply-templates-in-xsl">name/call-templates should be avoided where possible.</a> Change it to the below and it should work as expected when using the <code>apply-templates</code> you already have in the XSLT. <pre><code><xsl:template match="folder"> </code></pre> edit: A push style approach This might not be perfect, but a few things: * You skip over <code><folders></code> entirely, when they are the list, where as the <code><folder></code>s are the list items. * You appear to duplicate the item code for levels 1, 2 and 3. * You only ever make one item in the level 3 and above, all others would be ignored? Notice below, that I've defined how I want <code><folders></code> to be rendered, based on level, and how <code><folder></code>s are rendered independently. <pre><code><?xml version="1.0"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output method="html" omit-xml-declaration="yes" indent="yes"/> <xsl:template match="/"> <xsl:apply-templates/> </xsl:template> <xsl:template match="folders"> <ul> <xsl:attribute name="class"> <xsl:text>nav-l</xsl:text> <xsl:choose> <xsl:when test="@level&gt;2"> <xsl:text>s nav-hidden</xsl:text> </xsl:when> <xsl:otherwise> <xsl:value-of select="@level"/> </xsl:otherwise> </xsl:choose> </xsl:attribute> <xsl:apply-templates/> </ul> </xsl:template> <xsl:template match="folder"> <li> <xsl:if test="@selected='Y'"> <xsl:attribute name="class">nav-active</xsl:attribute> </xsl:if> <a href="{@url}" class="nav-item"> <xsl:choose> <xsl:when test="child::*"> <xsl:attribute name="class">trigger-chan nav-next</xsl:attribute> <xsl:value-of select="@name"/> </xsl:when> <xsl:otherwise> <xsl:value-of select="@name"/> </xsl:otherwise> </xsl:choose> </a> <xsl:apply-templates select="folders"/> </li> </xsl:template> </xsl:stylesheet> </code></pre> Notice how the above template is shorter than your initial one, as repeated elements are removed. All <code><folder></code>s render the same, so only one template is needed. In fact, the <code><folder></code>s don't need to know their level, only the parent <code><folders></code> do, so that logic is moved to the correct template. People who are new to XSLT often overlook how <code>apply-templates</code> can be used effectively to define recursion and allow very clear separations between elements. When creating templates, try and focus on how this particular element should be represented, and knowing how its child elements may be required. Then, focus on a new template for the child elements and how those should be rendered and so on. Adding on to the above, always be on the look out for <code>../</code> in <code>@select</code>s or <code><value-of></code>s as it implies that your logic is dependant on elements that are outside the current "scope". Not always bad, but something to be aware of. Try and minimise <code>for-each</code> where possible and see if they can be rewritten to use <code>apply-templates</code>, and unless absolutely required for some odd reason try and never use <code>call-templates</code> as they are less functional.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to build a recursive navigation in XSL/XML
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. This table or related slice is empty.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to build a recursive navigation in XSL/XML
 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

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.