StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19694404
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-30T21:46:45.060
FavoriteCount
0
LastActivityDate
2013-10-31T01:58:16.217
LastEditDate
2013-10-31T01:58:16.217
LastEditorUserId
2571021
OwnerUserId
2571021
ParentId
19693694
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<p>You will only be able to tell it that attr1 is required, and attr2 and attr3 are optional. There is no way that I know off defining in a XSD schema (for XML 1.0) that you can't have both attr2 and attr3. You would have to have something validate it afterwards to check for that combination.</p> <pre><code><?xml version="1.0" encoding="utf-16"?> <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="root"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="node"> <xs:complexType> <xs:attribute name="attr1" type="xs:int" use="required" /> <xs:attribute name="attr2" type="xs:int" use="optional" /> <xs:attribute name="attr3" type="xs:int" use="optional" /> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> </code></pre> <p>EDIT: I came across another thread where someone wanted some complex validation like yours and a link was provided in one of the comments too an article talking about <a href="http://www.w3.org/wiki/Co-occurrence_constraints" rel="nofollow">Co-occurrence constraints</a> which is what you are after and was implement for XML version 1.1. I also come accross this article <a href="http://www.ibm.com/developerworks/library/x-xml11pt2/" rel="nofollow">XML Schema 1.1, Part 2: An introduction to XML Schema 1.1</a> that went into details. Unfortunately XML 1.1 does not seem to be widely supported.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConditionally pick same element but with different attribute list
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDijkgraaf
UserOwnerUserId
1. USDijkgraaf
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POConditionally pick same element but with different attribute list
  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
  VTAcceptedByOriginator
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COoh ok . Yea I think after the basic xml validation, I am just going to very the attribute combinations myself. Thanks!
  singulars
  PostPostId
  PO
  UserUserId
  USJoe

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.