StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3462553
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-08-11T20:33:03.127
FavoriteCount
0
LastActivityDate
2010-08-11T20:33:03.127
LastEditDate
LastEditorUserId
0
OwnerUserId
334519
ParentId
3459369
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Using one of the Haskell parser libraries can make this kind of thing much less painful and error-prone. Here's an example of how to do this with <a href="http://hackage.haskell.org/package/attoparsec" rel="nofollow noreferrer">Attoparsec</a>: <pre><code>module Main where import Control.Applicative import qualified Data.Map as M import Data.Attoparsec (maybeResult) import qualified Data.Attoparsec.Char8 as A import qualified Data.ByteString.Char8 as B type Environment = M.Map String String spaces = A.many $ A.char ' ' upTo delimiter = B.unpack <$> A.takeWhile (A.notInClass $ delimiter : " ") <* (spaces >> A.char delimiter >> spaces) entry = (,) <$> upTo ':' <*> upTo ';' environment :: A.Parser Environment environment = M.fromList <$> A.sepBy entry A.endOfLine parseEnvironment :: B.ByteString -> Maybe Environment parseEnvironment = maybeResult . flip A.feed B.empty . A.parse environment </code></pre> If we have a file <code>context.txt</code>: <pre><code>user: somebody; home: somewhere; x: 1; y: 2; z: 3; </code></pre> We can test the parser as follows: <pre><code>*Main> Just env <- parseEnvironment <$> B.readFile "context.txt" *Main> print $ M.lookup "user" env Just "somebody" *Main> print env fromList [("home","somewhere"),("user","somebody"),("x","1"),("y","2"),("z","3")] </code></pre> Note that I'm using a <code>Map</code> to represent the environment, as camcann suggested in a comment on your previous <code>Reader</code> monad question.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POstrange behavior reading a file
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTravis Brown
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POstrange behavior reading a file
 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.