StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
889156
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-05-20T17:15:51.333
FavoriteCount
0
LastActivityDate
2009-05-20T18:14:03.697
LastEditDate
2009-05-20T18:14:03.697
LastEditorUserId
48082
OwnerUserId
48082
ParentId
888810
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<p>Maybe something like this?</p> <pre><code><schema elementFormDefault = "qualified" xmlns = "http://www.w3.org/2001/XMLSchema" xmlns:xs = "http://www.w3.org/2001/XMLSchema" xmlns:tns = "urn:cheeso.examples.2009.05.listofbooks" targetNamespace = "urn:cheeso.examples.2009.05.listofbooks" > <element name="Shelf" nillable="true" type="tns:BookShelf" /> <complexType name="BookShelf"> <sequence> <element minOccurs="0" maxOccurs="1" name="Store" type="tns:ArrayOfChoice1" /> </sequence> </complexType> <complexType name="ArrayOfChoice1"> <choice minOccurs="0" maxOccurs="unbounded"> <element minOccurs="1" maxOccurs="1" name="newBook" nillable="true" type="tns:newBook" /> <element minOccurs="1" maxOccurs="1" name="oldBook" nillable="true" type="tns:oldBook" /> </choice> </complexType> <complexType name="Book"> <attribute name="name" type="string" /> </complexType> <complexType name="newBook"> <complexContent mixed="false"> <extension base="tns:Book" /> </complexContent> </complexType> <complexType name="oldBook"> <complexContent mixed="false"> <extension base="tns:Book" /> </complexContent> </complexType> </schema> </code></pre> <p>Of course you could simplify to </p> <pre><code><schema elementFormDefault = "qualified" xmlns = "http://www.w3.org/2001/XMLSchema" xmlns:xs = "http://www.w3.org/2001/XMLSchema" xmlns:tns = "urn:cheeso.examples.2009.05.listofbooks" targetNamespace = "urn:cheeso.examples.2009.05.listofbooks" > <element name="Shelf" nillable="true" type="tns:BookShelf" /> <complexType name="BookShelf"> <sequence> <element minOccurs="0" maxOccurs="1" name="Store" type="tns:ArrayOfChoice1" /> </sequence> </complexType> <complexType name="ArrayOfChoice1"> <choice minOccurs="0" maxOccurs="unbounded"> <element minOccurs="1" maxOccurs="1" name="newBook" nillable="true" type="xs:string" /> <element minOccurs="1" maxOccurs="1" name="oldBook" nillable="true" type="xs:string" /> </choice> </complexType> </schema> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJAXB List of Choice
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCheeso
UserOwnerUserId
1. USCheeso
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. This table or related slice is empty.
CommentsPostId
1. COThank you for your answer. Sorry, but I was unclear in my question. Both oldBook and newBook will contain common fields as well as different and I want to avoid casting in Java code. In schema described above, when oldBook and newBook has the string type, JAXB will generate List of JAXBElement<String> and instead of instanceof and casting one has to call getName on JAXBElement to determine required type of element. May be this situation is wrong for XML design? And I should separate oldBook and newBook enumeration?
  singulars
  PostPostId
  PO
  UserUserId
  USolek
2. COYou may have an overconstrained problem, I suspect. I don't know so much about JAXB and the possibility to shape the object model generated from the XSD. Distinguishing data of the same type by element name alone, requires your program to call getName(). If you change the shape of the schema, you could use <book name="bookname" type="new" />, in which case you would not have to call getName(). Instead you would have a different object model. Or you could specify new complexTypes for newBook and oldBook, as in my first example schema. It's up to you.
  singulars
  PostPostId
  PO
  UserUserId
  USCheeso

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.