StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9363977
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-02-20T15:48:26.767
FavoriteCount
0
LastActivityDate
2012-02-20T15:53:57.187
LastEditDate
2012-02-20T15:53:57.187
LastEditorUserId
36305
OwnerUserId
36305
ParentId
9363388
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
This OP has conceiled the most important fact about the XML document -- as he tells us in a later comment, "The XML uses a namespace" ... Here is a solution to this so late-clarified question: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:x="some:namespace" xmlns="some:namespace" exclude-result-prefixes="x"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:strip-space elements="*"/> <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select="node()|@*"/> </xsl:copy> </xsl:template> <xsl:template match="x:F"> <G> <xsl:apply-templates/> </G> </xsl:template> </xsl:stylesheet> </code></pre> when this transformation is applied on the following XML document (based on the namespace the OP admitted...): <pre><code><T xmlns="some:namespace"> <A> <C> </C> </A> <D> <E>Data</E> <F>Data</F> </D> </T> </code></pre> the wanted, correct result is produced: <pre><code><T xmlns="some:namespace"> <A> <C /> </A> <D> <E>Data</E> <G>Data</G> </D> </T> </code></pre> Explanation: The problem in the original code is here: <pre><code> <xsl:template match="F"> </code></pre> This template matches an element <code>F</code> that is in no namespace. However all elements of the real XML document are in some undisclosed namespace -- not in no namespace. Therefore, the above template cannot match an <code>F</code> element in no namespace, because no such (<code>F</code> element in no namespace) exists. The solution is to define the same namespace in the XSLT transformation and to have the template match an <code>F</code> element in that namespace.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXML Specific node template not matching
 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. POXML Specific node template not matching
 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
CommentsPostId
1. COApologies for omitting the detail but my experience with XSL is rediculously small. It has solved the issue though.
 singulars
 PostPostId
 PO
 UserUserId
 USMike
2. CO@Mike: Details are important. Otherwise we could explain any problem with the bad weather.
 singulars
 PostPostId
 PO
 UserUserId
 USDimitre Novatchev

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.