StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2813887
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-05-11T19:38:26.933
FavoriteCount
0
LastActivityDate
2010-05-11T20:01:35.640
LastEditDate
2010-05-11T20:01:35.640
LastEditorUserId
214222
OwnerUserId
214222
ParentId
2813823
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
The best solution is to remove the <code><type/></code> element and only have a <code>xs:choice</code> for <code><a/></code> and <code></code> and let the application consuming the xml sort out the type. Another solution might be to have a <code>xs:choice</code> for <code><a/></code> and <code></code> use an xslt script to do a validation of the <code><type/></code> element in relation to <code><a/></code> and <code></code>. First validate the xml against the xmlschema then use the xslt to do a transformation on it, if the result of the transform is empty string it is valid otherwise show the resulting string as an error message. Something like this... XmlSchema: <pre><code> <xs:element name="some-element"> <xs:complexType> <xs:sequence> <xs:element name="type" type="xs:integer" /> <xs:choice> <xs:element name="a" type="xs:string" /> <xs:element name="b" type="xs:string" /> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> </code></pre> Xslt: <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:demo="uri:demo:namespace"> <xsl:output method="text" /> <xsl:template match="/demo:some-element"> <xsl:if test="type = 1 and not(demo:a)"> When type equals 1 element a is requred. </xsl:if> <xsl:if test="type = 2 and not(demo:b)"> When type equals 2 element b is requred. </xsl:if> </xsl:template> </xsl:stylesheet> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODifferent sub-elements depending on attribute/element value
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJens Granlund
UserOwnerUserId
1. USJens Granlund
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. 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.