StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18509257
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2013-08-29T11:06:43.360
FavoriteCount
0
LastActivityDate
2013-08-29T12:34:19.823
LastEditDate
2013-08-29T12:34:19.823
LastEditorUserId
592139
OwnerUserId
592139
ParentId
18508709
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
XSLT 2.0 has <code>xsl:analyze-string</code> which is designed for precisely this task, so if at all possible I suggest you upgrade to a 2.0 processor such as <a href="http://www.saxonica.com/welcome/welcome.xml" rel="nofollow">Saxon</a>: <pre><code><xsl:template match="node"> <failure> <xsl:analyze-string select="failure" regex="^\s*CRS\s*(\S+)\s*(not\s*.*)$" flags="m"> <xsl:matching-substring> <CRS> <id><xsl:value-of select="regex-group(1)" /></id> <result><xsl:value-of select="normalize-space(regex-group(2))" /></result> </CRS> </xsl:matching-substring> </xsl:analyze-string> </failure> </xsl:template> </code></pre> String manipulation facilities in XSLT 1.0 are extremely limited in comparison, and since XSLT is a functional language without updateable variables you'd have to write some sort of hideously complex set of recursive <code>call-template</code> logic to split up the text into separate lines and then extract the relevant bits out of each line in turn using <code>substring-before</code> and <code>substring-after</code>. <pre><code><xsl:template name="each-line"> <xsl:param name="val" />  <xsl:variable name="firstLine" select="normalize-space(substring-before($val, '&#10;'))" />  <xsl:variable name="rest" select="substring-after($val, '&#10;')" /> <xsl:if test="$firstLine"> <xsl:call-template name="process-line"> <xsl:with-param name="line" select="$firstLine" /> </xsl:call-template> </xsl:if>  <xsl:if test="normalize-space($rest)"> <xsl:call-template name="each-line"> <xsl:with-param name="val" select="$rest" /> </xsl:call-template> </xsl:if> </xsl:template> <xsl:template name="process-line"> <xsl:param name="line" /> <xsl:if test="starts-with($line, 'CRS ') and contains($line, ' not ')">  <CRS>  <id><xsl:value-of select="substring-before(substring-after($line, ' '), ' ')" /></id>  <result><xsl:value-of select="substring-after(substring-after($line, ' '), ' ')" /></result> </CRS> </xsl:if> </xsl:template> </code></pre> You would call this logic using a construct like <pre><code><xsl:template match="node"> <failure> <xsl:call-template name="each-line"> <xsl:with-param name="val" select="failure" /> </xsl:call-template> </failure> </xsl:template> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT - get sorted information extract from cdata
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USIan Roberts
UserOwnerUserId
1. USIan Roberts
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POXSLT - get sorted information extract from cdata
 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

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.