StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2900653
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-05-24T22:03:00.483
FavoriteCount
0
LastActivityDate
2010-05-25T10:00:16.560
LastEditDate
2010-05-25T10:00:16.560
LastEditorUserId
18771
OwnerUserId
18771
ParentId
2899484
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Here is what I would do: <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="text()[preceding-sibling::node()[1][self::c]]">  <xsl:text>Hello world</xsl:text> </xsl:template> </xsl:stylesheet> </code></pre> Note that text nodes contain "surrounding" whitespace - in the sample XML in the question the matched text node is whitespace only, which is why the above works. It will stop to work as soon as the input document looks like this: <pre><code><a><c/></a> </code></pre> because here is no text node following <code><c></code>. So if this is too brittle for your use case, an alternative would be: <pre><code> <xsl:template match="c"> <xsl:copy-of select="." /> <xsl:text>Hello world</xsl:text> </xsl:template>  <xsl:template match="text()[preceding-sibling::node()[1][self::c]]" /> </code></pre> In any case, stuff like the above makes clear why intermixing of text nodes and element nodes is best avoided. This is not always possible (see XHTML). But when you have the chance and the XML is supposed to be purely a container for structural data, staying clear of mixed content makes your life easier.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT: add node inner text
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTomalak
UserOwnerUserId
1. USTomalak
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POXSLT: add node inner text
 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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COAny of your solutions produce the error: Only 'child' and 'attribute' axes are allowed in a pattern outside predicates. c/ -->following-sibling::<-- node()[1][self::text()]
 singulars
 PostPostId
 PO
 UserUserId
 USNabo
2. CO@nabo: Oh, my bad. I've corrected the match pattern.
 singulars
 PostPostId
 PO
 UserUserId
 USTomalak

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.