StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2493702
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-22T15:58:08.507
FavoriteCount
0
LastActivityDate
2010-03-22T16:54:41.683
LastEditDate
2017-05-23T09:57:53.307
LastEditorUserId
-1
OwnerUserId
211232
ParentId
2491678
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
If I understand correctly, you wish that you could write Schema like this: <pre><code> <xs:complexType name="composite-key"> <xs:choice maxOccurs="unbounded"> <xs:element name="key" type="simple-key"/> <xs:element name="key" type="composite-key"/> </xs:choice> <xs:attribute name="name" type="xs:string" use="required"/> </xs:complexType> </code></pre> simple-key would be defined elsewhere. This is not valid Schema since you are not allowed to use the same element name twice. If Schema supported this, it would have a devil of a time disambiguating element types based upon their structure alone. If you have control over the XML, you can make this work by changing one or both of the element names. For example, one might use val for simple values and obj for composite ones: <pre><code><xs:complexType name="composite-key"> <xs:choice maxOccurs="unbounded"> <xs:element name="val" type="simple-key"/> <xs:element name="obj" type="composite-key"/> </xs:choice> <xs:attribute name="name" type="xs:string" use="required"/> </xs:complexType> </code></pre> Adjust the names to taste. This would be my recommended solution as it emphasizes clarity. However, the element names may be out of your control. If so, a less satisfactory solution would be as follows: <pre><code><xs:complexType name="key" mixed="true"> <xs:sequence maxOccurs="unbounded"> <xs:element name="key" type="key"/> </xs:sequence> <xs:attribute name="name" type="xs:string" use="required"/> <xs:attribute name="type" type="xs:string"/> <xs:attribute name="representation" type="xs:string"/> </xs:complexType> </code></pre> The key differences here are the mixed content type, and the unfortunate fact that the declaration is now an amalgam of the simple and composite key types. I say that this is "less satisfactory" because now you must perform additional validity checking in your own code, after Schema has finished with it. For example, you would need to validate whether the set of attributes given make sense for the implied key type. Also, the example as written would permit text to appear anywhere between nested key elements -- probably something you do not want. [edit: the same question is discussed on stackoverflow <a href="https://stackoverflow.com/questions/2468843/how-define-several-elements-with-same-name-but-different-type-in-xsdchoice-elem/2494088#2494088">here</a>]
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSD schema for recursive XML
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USWReach
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
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.