StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
883122
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-05-19T14:28:17.280
FavoriteCount
0
LastActivityDate
2011-08-29T09:21:27.563
LastEditDate
2011-08-29T09:21:27.563
LastEditorUserId
97569
OwnerUserId
97569
ParentId
882631
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
I found out myself. The difference between my examples is not very obvious on the first glance, but if the example had been a little more complex it would have made sense. The following extension clarifies the differences: <pre> <code> <xsd:element name="XList"> <xsd:complexType> <xsd:sequence> <xsd:element name="X" type="xsd:token" minOccurs="1" maxOccurs="1"/> <xsd:element name="Y" type="xsd:token" minOccurs="1" maxOccurs="1"/> </xsd:sequence> </xsd:complexType> </xsd:element> </code> </pre> leads to <pre> <code> <XList> <X>Only X</X> <Y>Only Y</Y> </XList> </code> </pre> whereas <pre> <code> <xsd:element name="XList"> <xsd:complexType> <xsd:sequence> <xsd:element name="X" type="xsd:token" minOccurs="1" maxOccurs="unbounded"/> <xsd:element name="Y" type="xsd:token" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element> </code> </pre> leads to <pre> <code> <XList> <X>First X</X> <X>Second X</X> <X>Third X</X> ... <Y>First Y</Y> <Y>Second Y</Y> ... </XList> </code> </pre> and <pre> <code> <xsd:element name="XList"> <xsd:complexType> <xsd:sequence minOccurs="1" maxOccurs="unbounded" > <xsd:element name="X" type="xsd:token" minOccurs="2" maxOccurs="2"/> <xsd:element name="Y" type="xsd:token" minOccurs="1" maxOccurs="1"/> </xsd:sequence> </xsd:complexType> </xsd:element> </code> </pre> leads to <pre> <code> <XList> <X>First X</X> <X>Second X</X> <Y>First Y</Y> <X>Third X</X> <X>Fourth X</X> <Y>Second Y</Y> ... </XList> </code> </pre> and <pre> <code> <xsd:element name="XList"> <xsd:complexType> <xsd:sequence minOccurs="1" maxOccurs="unbounded" > <xsd:element name="X" type="xsd:token" minOccurs="1" maxOccurs="unbounded"/> <xsd:element name="Y" type="xsd:token" minOccurs="1" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element> </code> </pre> leads to <pre> <code> <XList> <X>First X</X> <X>Second X</X> <X>Third X</X> ... <Y>First Y</Y> <Y>Second Y</Y> ... <X>Fourth X</X> <X>Fifth X</X> <X>Sixth X</X> ... <Y>Third Y</Y> <Y>Fourth Y</Y> ... </XList> </code> </pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsage of XSD occurrence Indicators
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDynamicbyte
UserOwnerUserId
1. USDynamicbyte
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsage of XSD occurrence Indicators
 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
3. 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.