StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19167552
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-03T19:24:58.577
FavoriteCount
0
LastActivityDate
2013-10-03T19:24:58.577
LastEditDate
LastEditorUserId
0
OwnerUserId
2824390
ParentId
19164515
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
If you want to stick with strictly <code>gson</code> you can provide a custom <a href="http://google-gson.googlecode.com/svn/tags/gson-1.7.1/docs/javadocs/com/google/gson/JsonDeserializer.html" rel="nofollow">deserializer</a>. Since we know that <code>service</code> is either a property of the base <code>json</code> string or embedded within some other <code>property</code>, we can use the deserializer to step-wise parse out the offending components and handle them accordingly. <pre><code> public class MyJsonDeserializer implements JsonDeserializer<YourParsedData> { @Override public YourParsedData deserialize(final JsonElement je, final Type type, final JsonDeserialization Context jdc) throws JsonParseException { final JsonObject obj = je.getAsJsonObject(); //our original full json string final JsonElement serviceElement = obj.get("service"); //here we provide the functionality to handle the naughty element. It seems emtpy string is returned as a JsonPrimitive... so one option if(serviceElement instanceOf JsonPrimitive) { //it was empty do something } return YourParsedData.create(); //provide the functionality to take in the parsed data } } </code></pre> The custom deserializer would be called as follows: <pre><code> final Gson gson = new GsonBuilder().registerTypeAdapter(YourParsedData.class, new MyJsonDeserializer()).create(); gson.fromJson("{service: ''}", YourParsedData.class); </code></pre> I typed all this up so if I missed some syntax my apologies.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGSON parsing unspecified type variable
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOrigineil
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGSON parsing unspecified type variable
 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
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.