StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19525615
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-22T18:30:54.457
FavoriteCount
0
LastActivityDate
2013-10-22T18:30:54.457
LastEditDate
LastEditorUserId
0
OwnerUserId
1029225
ParentId
19524511
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Well, there are a couple of things worth pointing out here: Firstly, you've annotated the <code>pokemon</code> field in the <code>Data</code> class, but this is not going to work unless you supply the name of the xml tag the field should be bound up to. SimpleXML won't know that you actually mean the bind up <code>Pkmn</code> to <code>pokemon</code>. In short, add: <pre><code>@Element(name="Pkmn") private Pokemon pokemon; </code></pre> Last time I checked, SimpleXML does support auto-binding, but that will require the <a href="http://simple.sourceforge.net/download/stream/doc/javadoc/org/simpleframework/xml/Default.html" rel="nofollow"><code>@Default</code> annotation</a> and the field names have to match the xml tags. That being said, the safest option here is to not use <code>@Default</code> and explicitly supply the name with every annotation. That is, go through your <code>Pokemon</code> class and declare the name for every <code>@Element</code> annotation. For example: <pre><code>... @Element(name="ablt") private String abilities; ... </code></pre> After that, you should be close to have working code. To clean up, you may want to remove <code>strict=false</code> from the <code>@Root</code> declaration of your <code>Data</code> class. That was probably your initial attempt to bypass the <code>ValueRequiredException</code>? If the <code>Data</code> tag not having a <code>Pkmn</code> tag is a valid scenario, then potentially leave it in there, but otherwise you should remove it to avoid undesired side effects.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSimple-framework XML deserializing ValueRequiredException
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMH.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSimple-framework XML deserializing ValueRequiredException
 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. COThank you sir. Worked a charm.
 singulars
 PostPostId
 PO
 UserUserId
 USJoe Austin

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.