StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20511725
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-12-11T06:05:00.187
FavoriteCount
0
LastActivityDate
2013-12-11T08:24:48.047
LastEditDate
2013-12-11T08:24:48.047
LastEditorUserId
317052
OwnerUserId
317052
ParentId
20511295
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Each error is about an undeclared element. To resolve these specific errors, you would need to declare every element that is referenced in your DTD. (Add <code><!ELEMENT</code> declarations for <code>name</code>, <code>developer</code>, <code>engine</code>, etc.) Also, you have <code>name</code>, <code>developer</code>, <code>engine</code>, etc. declared as attributes (<code><!ATTLIST</code>). Instead of just resolving the errors, you should probably decide what you want to be an element and what you want to be an attribute. Here are some examples. (The DTDs and XML are together to make it easier to test. (The DTD is in an internal subset.) The DTDs can be separated.): Using Elements <pre><code><!DOCTYPE gamelist [ <!ELEMENT gamelist (game*)> <!ELEMENT game (data,metadata)> <!ELEMENT data (name,developer,engine?,releasedate?)> <!ELEMENT metadata (hoursplayed?,lastplayed?,lastdataupdate)> <!ELEMENT name (#PCDATA)> <!ELEMENT developer (#PCDATA)> <!ELEMENT engine (#PCDATA)> <!ELEMENT releasedate (#PCDATA)> <!ELEMENT hoursplayed (#PCDATA)> <!ELEMENT lastplayed (#PCDATA)> <!ELEMENT lastdataupdate (#PCDATA)> ]> <gamelist> <game> <data> <name></name> <developer></developer> <engine></engine> <releasedate></releasedate> </data> <metadata> <hoursplayed></hoursplayed> <lastplayed></lastplayed> <lastdataupdate></lastdataupdate> </metadata> </game> </gamelist> </code></pre> Using Attributes <pre><code><!DOCTYPE gamelist [ <!ELEMENT gamelist (game*)> <!ELEMENT game (data,metadata)> <!ELEMENT data EMPTY> <!ATTLIST data name CDATA #REQUIRED developer CDATA #REQUIRED engine CDATA #IMPLIED releasedate CDATA #IMPLIED > <!ELEMENT metadata EMPTY> <!ATTLIST metadata hoursplayed CDATA #IMPLIED lastplayed CDATA #IMPLIED lastdataupdate CDATA #REQUIRED> ]> <gamelist> <game> <data name="" developer="" engine="" releasedate=""/> <metadata hoursplayed="" lastplayed="" lastdataupdate=""/> </game> </gamelist> </code></pre> Here are some links that might help: <a href="http://www.w3.org/standards/xml/core" rel="nofollow">XML Essentials</a> (Start here first.) <a href="http://www.w3.org/TR/REC-xml/" rel="nofollow">XML 1.0</a> (Specifically "<a href="http://www.w3.org/TR/REC-xml/#sec-logical-struct" rel="nofollow">Logical Structures</a>".) (Alternatively: <a href="http://www.w3.org/TR/xml11/" rel="nofollow">XML 1.1</a> ("<a href="http://www.w3.org/TR/xml11/#sec-logical-struct" rel="nofollow">Logical Structures</a>"))
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODefining XML tags/namespaces? Unrecognized warnings
 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. This table or related slice is empty.
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
CommentsPostId
1. COWould you mind showing me a short example? Say I wanted to define name as a required string (I'm just finding so many styles online and I can't differentiate between DTD and other uses of XML).
 singulars
 PostPostId
 PO
 UserUserId
 USI ate some tau
2. CO@Iatesometau - Please see my update.
 singulars
 PostPostId
 PO
 UserUserId
 USDaniel Haley

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.