StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4231758
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-20T07:49:24.983
FavoriteCount
0
LastActivityDate
2018-04-05T18:29:48.473
LastEditDate
2018-04-05T18:29:48.473
LastEditorUserId
317052
OwnerUserId
317052
ParentId
4231135
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
The issue is that you're trying to parse SGML with an XML tool. They're not the same. If you want to use an XML tool/language to access the data, you will probably need to convert the SGML to XML before trying to parse it. Ideally you'd either use a language/tool that supports SGML (like OmniMark) or something that can handle "XML like" data (like nokogiri from the first answer?). This can be pretty straight forward, but can get tricky at some points. Especially if you're talking about multiple doctypes (DTD's). (Also, there's no such thing as "well-formed" SGML. Yes, the elements/etc. have to be nested correctly but SGML has to have a DTD.) Here are some differences between SGML and XML that you'd need to handle. (You may not want to go this route, but it may be helpful for informational purposes anyway.): <ol> <li>DOCTYPE declaration The DOCTYPE declaration in your example is a perfectly valid SGML doctype. The <code>[]</code> (internal subset) doesn't have to have anything in it. If you do have declarations in the internal subset (usually entity declarations), you're more than likely going to have to keep a doctype declaration in the XML. The issue the XML parser is having is that you don't have a system identifier in the declaration. In an XML doctype declaration, the system identifier is required if there is a public identifier. In an SGML doctype declaration, it's not required. Bottom line: unless you need the XML to parse to a DTD/Schema or have declarations in the internal subset, strip the doctype declaration. If the XML does have to be valid, you'll at least need to add a system identifier. Don't forget to add the <code><?xml ...?></code> processing instruction.</li> <li>Elements without end tags The <code><hardhyphen></code> and <code><hyphen></code> elements are valid SGML. SGML DTD's allow you to specify tag minimization. What this means is that you can specify whether or not an end tag is required. (You can also make the start tag optional, but that's crazy talk.) In XML you have to close these elements (like <code><hardhyphen/></code> or <code><hardhyphen></hardhyphen></code>) The best thing to do is to look at your SGML DTD and see what elements have optional end tags. The tag minimization is specified right after the element name in the element declaration. A '-' means the tag is required. An 'o' (letter 'oh') means that the tag is optional. For example if you see <code><!ELEMENT hyphen - o (#PCDATA)></code>, this means that the start tag is required (<code>-</code>) and the end tag is optional (<code>o</code>). If you see <code><!ELEMENT hyphen - - (#PCDATA)></code>, both the start and the end tags are required. Bottom line: properly close all of the elements that don't have end tags</li> <li>Processing instructions Processing instructions (PI's) in SGML don't have the second <code>?</code> when they are closed like XML does. You'll need to add the second <code>?</code>. Example SGML PI: <code><?asdf jkl></code> Example XML PI: <code><?asdf jkl?></code></li> <li>Inclusions/Exclusions You probably won't have to worry about this, but in an SGML DTD you can specify in an element declaration that another element is allowed anywhere inside of that element (or not allowed). This can be a pain if your target XML needs to parse to a DTD; XML DTD's do not allow inclusions/exclusions. This is what an inclusion might look like: <code><!ELEMENT chapter - - (section)+ +(revst|revend)></code> This is saying that <code>revst</code> or <code>revend</code> are allowed anywhere inside of <code>chapter</code>. If the element declaration had <code>-(revst|revend)</code>, it would mean that <code>revst</code> or <code>revend</code> is not allowed anywhere inside of <code>chapter</code>.</li> </ol> Hope this helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POStrategy for parsing LOTS and LOTS of not-so-well formed SGML / XML documents
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDaniel Haley
UserOwnerUserId
1. USDaniel Haley
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POStrategy for parsing LOTS and LOTS of not-so-well formed SGML / XML documents
 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. 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.