StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3378562
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
14
CommunityOwnedDate
CreationDate
2010-07-31T14:41:53.140
FavoriteCount
0
LastActivityDate
2010-07-31T20:59:16.673
LastEditDate
2010-07-31T20:59:16.673
LastEditorUserId
36305
OwnerUserId
36305
ParentId
3360017
PostTypeId
2
Score
135
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> why did the former code outputs TEXT, why should I insist XSL to ignore all other text? is that the behavior of all XML parsers or only of my own </blockquote> You are discovering one of the most fundamental XSLT features as specified in the Specification: the <a href="http://www.w3.org/TR/xslt#built-in-rule" rel="noreferrer">built-in templates of XSLT</a>. From <a href="http://www.w3.org/TR/xslt#built-in-rule" rel="noreferrer">the Spec</a>: <blockquote> There is a built-in template rule to allow recursive processing to continue in the absence of a successful pattern match by an explicit template rule in the stylesheet. This template rule applies to both element nodes and the root node. The following shows the equivalent of the built-in template rule: <pre><code><xsl:template match="*|/"> <xsl:apply-templates/> </xsl:template> </code></pre> There is also a built-in template rule for each mode, which allows recursive processing to continue in the same mode in the absence of a successful pattern match by an explicit template rule in the stylesheet. This template rule applies to both element nodes and the root node. The following shows the equivalent of the built-in template rule for mode m. <pre><code><xsl:template match="*|/" mode="m"> <xsl:apply-templates mode="m"/> </xsl:template> </code></pre> There is also a built-in template rule for text and attribute nodes that copies text through: <pre><code><xsl:template match="text()|@*"> <xsl:value-of select="."/> </xsl:template> </code></pre> The built-in template rule for processing instructions and comments is to do nothing. <pre><code><xsl:template match="processing-instruction()|comment()"/> </code></pre> The built-in template rule for namespace nodes is also to do nothing. There is no pattern that can match a namespace node; so, the built-in template rule is the only template rule that is applied for namespace nodes. The built-in template rules are treated as if they were imported implicitly before the stylesheet and so have lower import precedence than all other template rules. Thus, the author can override a built-in template rule by including an explicit template rule. </blockquote> So, the reported behavior is the result of the application of the built-in templates -- the 1st and 2nd of all three of them. It is a good XSLT design pattern to override the built-in templates with your own that will issue an error message whenever called so that the programmer immediately knows his transformation is "leaking": For example, if there is this XML document: <pre><code><a> <c>Don't want to see this</c> </a> </code></pre> and it is processed with this transformation: <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:template match="a|b"> <xsl:copy> <xsl:attribute name="name"> <xsl:value-of select="name()"/> </xsl:attribute> <xsl:apply-templates/> </xsl:copy> </xsl:template> </xsl:stylesheet> </code></pre> the result is: <pre><code><a name="a"> Don't want to see this </a> </code></pre> and the programmer will be greatly confused how the unwanted text appeared. However, just adding this <code>catch-all template</code> helps avoid any such confusion and catch errors immediately: <pre><code> <xsl:template match="*"> <xsl:message terminate="no"> WARNING: Unmatched element: <xsl:value-of select="name()"/> </xsl:message> <xsl:apply-templates/> </xsl:template> </code></pre> Now, besides the confusing output the programmer gets a warning that explains the problem immediately: <pre><code> WARNING: Unmatched element: c </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy does XSLT output all text by default?
 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. POWhy does XSLT output all text by default?
 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
 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.