StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20685513
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-12-19T15:29:25.577
FavoriteCount
0
LastActivityDate
2013-12-19T15:44:38.120
LastEditDate
2013-12-19T15:44:38.120
LastEditorUserId
1015802
OwnerUserId
1015802
ParentId
20679096
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I think the "leading hex character" is a byte order mark (BOM) as I commented on your question, though I can't be sure without actually seeing it. The C++ parser seems not to know about BOMs, which is odd (see <a href="http://www.joelonsoftware.com/articles/Unicode.html" rel="nofollow">standard reference by Joel Spolsky</a>). Let's assume that the C++ parser works only with XML encoded as UTF-8 or one of its character subsets (ASCII, ISO-8859-1, etc.). In that case you have no option but to encode as UTF-8 but exclude the BOM. <code>XmlWriter</code> lets you do so as follows: <pre><code>var utf8NoBom = new UTF8Encoding(false); var writer = XmlWriter.Create(fs, new XmlWriterSettings() { Encoding = utf8NoBom } ); </code></pre> The quote below is from the MSDN reference on <a href="http://msdn.microsoft.com/en-us/library/ms162617%28v=vs.110%29.aspx" rel="nofollow">XmlWriter.Create</a>: <blockquote> XmlWriter always writes a Byte Order Mark (BOM) to the underlying data stream; however, some streams must not have a BOM. To omit the BOM, create a new XmlWriterSettings object and set the Encoding property to be a new UTF8Encoding object with the Boolean value in the constructor set to false. </blockquote> EDIT: If the C++ parser is a general-purpose XML parser then its ignorance of BOMs is odd. If the parser is domain-specific, i.e. if it is always used with files whose character encoding is known (and obviously limited), then its ignorance is not odd. I think this is Spolsky's point.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXmlTextWriter default encoding behaves differently to setting encoding to UTF-8
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USgroverboy
UserOwnerUserId
1. USgroverboy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POXmlTextWriter default encoding behaves differently to setting encoding to UTF-8
 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
CommentsPostId
1. COPerfect, thanks!
 singulars
 PostPostId
 PO
 UserUserId
 USAidan

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.