StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3841089
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2010-10-01T16:20:28.310
FavoriteCount
0
LastActivityDate
2010-10-01T16:20:28.310
LastEditDate
LastEditorUserId
0
OwnerUserId
0
ParentId
3840040
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
From <a href="http://www.w3.org/TR/2008/REC-xml-20081126/#sec-line-ends" rel="noreferrer">http://www.w3.org/TR/2008/REC-xml-20081126/#sec-line-ends</a> <blockquote> XML parsed entities are often stored in computer files which, for editing convenience, are organized into lines. These lines are typically separated by some combination of the characters CARRIAGE RETURN (#xD) and LINE FEED (#xA). To simplify the tasks of applications, the XML processor MUST behave as if it normalized all line breaks in external parsed entities (including the document entity) on input, before parsing, by translating both the two-character sequence #xD #xA and any <code>#xD</code> that is not followed by #xA to a single #xA character. </blockquote> So, it's ok to look for <code>&#xA;</code> (or <code>&#10;</code>). But do note that white space only text nodes from the input may or may not be preserve depending on XML tree provider (MSXSL XML parser doesn't preserve this text nodes). Not white space only text nodes are preserved, of course. Then, this <code>text</code> named template replace new lines with empty <code>br</code> elements in XSLT 1.0: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" indent="yes"/> <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select="node()|@*"/> </xsl:copy> </xsl:template> <xsl:template match="text()" name="text"> <xsl:param name="pString" select="."/> <xsl:choose> <xsl:when test="contains($pString,'&#xA;')"> <xsl:call-template name="text"> <xsl:with-param name="pString" select="substring-before($pString,'&#xA;')"/> </xsl:call-template> <xsl:call-template name="text"> <xsl:with-param name="pString" select="substring-after($pString,'&#xA;')"/> </xsl:call-template> </xsl:when> <xsl:otherwise> <xsl:value-of select="$pString"/> </xsl:otherwise> </xsl:choose> </xsl:template> </xsl:stylesheet> </code></pre> With this input: <pre><code><root> <text> whatever </text> <text>and more</text> </root> </code></pre> Output: <pre><code><root> <text> whatever </text> <text>and more</text> </root> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODetecting incoming XML "CR" character, then converting to 
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
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. PODetecting incoming XML "CR" character, then converting to 
 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
1. CO@Alejandro: +1 for a correct answer and good explanation!
 singulars
 PostPostId
 PO
 UserUserId
 USDimitre Novatchev
2. COYay Alejandro, this was dead on. I'll next post my question about DOCTYPE in msmxl6 which seems to be non-working. Thank you!
 singulars
 PostPostId
 PO
 UserUserId
 USDave
3. CO@Dave: You are wellcome! Ask any time.
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.

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.