StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POXSD condition based on element value
primarykey
Id
12377592
data
AcceptedAnswerId
12397382
AnswerCount
2
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-09-11T20:41:15.277
FavoriteCount
0
LastActivityDate
2012-09-13T17:38:29.023
LastEditDate
2012-09-12T13:33:08.003
LastEditorUserId
1655087
OwnerUserId
1655087
ParentId
0
PostTypeId
1
Score
2
ViewCount
4700
LastEditorDisplayName
text
Body
I have a situation with an object that has 3 properties: 1) action 2) ID 3) Name <code>Action</code> can be <code>Update</code> or <code>Remove</code> and is mandatory. <code>ID</code> is an int and is mandatory. Name is a string and is Optional when <code>Action=Remove</code> and is mandatory when <code>Action=Update</code>. How do I describe this in XSD? Thank you! Jim This is what I have so far: <pre><code> <s:element name="UpdateAccount"> <s:complexType> <s:sequence> <s:element minOccurs="0" maxOccurs="1" name="myAccount" type="tns:WSUpdate" /> </s:sequence> </s:complexType> </s:element> <s:complexType name="WSUpdate"> <s:sequence> <s:element minOccurs="1" maxOccurs="1" name="ID" type="s:int" /> <s:element minOccurs="1" maxOccurs="1" name="Name" nillable="false" type="s:string" /> <s:element minOccurs="1" maxOccurs="1" name="action" type="tns:UpdateAction" /> </s:sequence> </s:complexType> <s:simpleType name="UpdateAction"> <s:restriction base="s:string"> <s:enumeration value="Update" /> <s:enumeration value="Remove" /> </s:restriction> </s:simpleType> </code></pre> EDIT Sep 12, 2012 @ 9:28am EST: After doing some more thinking, I have patched up something. This isn't exactly what I was looking for, but perhaps close enough for my client to accept. It doesn't exactly go into condition details, but it does give the structure definition to the client. What do you think? <pre><code> <s:element name="UpdateAccount"> <s:complexType> <s:sequence> <s:choice> <s:element minOccurs="0" maxOccurs="1" name="myAccount" type="tns:WSUpdate" /> <s:element minOccurs="0" maxOccurs="1" name="myAccount" type="tns:WSDelete" /> </s:choice> </s:sequence> </s:complexType> </s:element> <s:complexType name="WSUpdate"> <s:sequence> <s:element minOccurs="1" maxOccurs="1" name="ID" type="s:int" /> <s:element minOccurs="1" maxOccurs="1" name="Name" nillable="false" type="s:string" /> <s:element minOccurs="1" maxOccurs="1" name="action" type="tns:UpdateAction" /> </s:sequence> </s:complexType> <s:complexType name="WSDelete"> <s:sequence> <s:element minOccurs="1" maxOccurs="1" name="ID" type="s:int" /> <s:element minOccurs="0" maxOccurs="1" name="Name" nillable="true" type="s:string" /> <s:element minOccurs="1" maxOccurs="1" name="action" type="tns:UpdateAction" /> </s:sequence> </s:complexType> <s:simpleType name="UpdateAction"> <s:restriction base="s:string"> <s:enumeration value="Update" /> <s:enumeration value="Remove" /> </s:restriction> </s:simpleType> </code></pre>
Tags
<.net><xml><vb.net><xsd>
Title
XSD condition based on element value
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USGeorge
UserOwnerUserId
1. USGeorge
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POXSD condition based on element value
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POXSD condition based on element value
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COIn my experience, you dont use XSD to define situations of the elements but simply the way the Element/Attributes should be associated with each other, irregardless of their value. So if you have a situation where 3 Attribute/Elements will be Optional/Required based on certain situations you need to design for those unique situations.
 singulars
 PostPostId
 POXSD condition based on element value
 UserUserId
 USGoldBishop

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.