StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6096763
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-23T11:49:19.187
FavoriteCount
0
LastActivityDate
2012-05-16T03:28:18.127
LastEditDate
2012-05-16T03:28:18.127
LastEditorUserId
139117
OwnerUserId
298847
ParentId
6090599
PostTypeId
2
Score
25
ViewCount
0
LastEditorDisplayName
text
Body
I'd recommend that you use the new <a href="http://hackage.haskell.org/package/aeson" rel="noreferrer">aeson</a> package instead of the <a href="http://hackage.haskell.org/package/json" rel="noreferrer">json</a> package, as the former performs much better. Here's how you'd convert a JSON object to a Haskell record, using aeson: <pre><code>{-# LANGUAGE OverloadedStrings #-} module Example where import Control.Applicative import Control.Monad import Data.Aeson data Tweet = Tweet { from_user :: String, to_user_id :: String, profile_image_url :: String, created_at :: String, id_str :: String, source :: String, to_user_id_str :: String, from_user_id_str :: String, from_user_id :: String, text :: String, metadata :: String } instance FromJSON Tweet where parseJSON (Object v) = Tweet <$> v .: "from_user" <*> v .: "to_user_id" <*> v .: "profile_image_url" <*> v .: "created_at" <*> v .: "id_str" <*> v .: "source" <*> v .: "to_user_id_str" <*> v .: "from_user_id_str" <*> v .: "from_user_id" <*> v .: "text" <*> v .: "metadata" -- A non-Object value is of the wrong type, so use mzero to fail. parseJSON _ = mzero </code></pre> Then use <code>Data.Aeson.json</code> to get a <a href="http://hackage.haskell.org/package/attoparsec" rel="noreferrer">attoparsec</a> parser that converts a <code>ByteString</code> into a <code>Value</code>. The call <code>fromJSON</code> on the <code>Value</code> to attempt to parse it into your record. Note that there are two different parsers involved in these two steps, a <code>Data.Attoparsec.Parser</code> parser for converting the <code>ByteString</code> into a generic JSON <code>Value</code> and then a <code>Data.Aeson.Types.Parser</code> parser for converting the JSON value into a record. Note that both steps can fail: <ul> <li>The first parser can fail if the <code>ByteString</code> isn't a valid JSON value.</li> <li>The second parser can fail if the (valid) JSON value doesn't contain one of the fields you mentioned in your <code>fromJSON</code> implementation. </li> </ul> The aeson package prefers the new Unicode type <code>Text</code> (defined in the <a href="http://hackage.haskell.org/package/text" rel="noreferrer">text</a> package) to the more old school <code>String</code> type. The <code>Text</code> type has a much more memory efficient representation than <code>String</code> and generally performs better. I'd recommend that you change the <code>Tweet</code> type to use <code>Text</code> instead of <code>String</code>. If you ever need to convert between <code>String</code> and <code>Text</code>, use the <code>pack</code> and <code>unpack</code> functions defined in <code>Data.Text</code>. Note that such conversions require O(n) time, so avoid them as much as possible (i.e. always use <code>Text</code>).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POParsing JSON string into record in Haskell
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USVlad the Impala
UserOwnerUserId
1. UStibbe
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
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.