StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6350956
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-06-14T22:32:57.153
FavoriteCount
0
LastActivityDate
2011-06-15T16:57:08.473
LastEditDate
2011-06-15T16:57:08.473
LastEditorUserId
112882
OwnerUserId
112882
ParentId
6350752
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
Parsers are actually type abbreviations for functions from streams to replies: <pre><code>Parser<_,_> is just CharStream<_> -> Reply<_> </code></pre> Keeping that in mind, you can easily write a custom parser for positions: <pre><code>let position : CharStream<_> -> Reply<Position> = fun stream -> Reply(stream.Position) (* OR *) let position : Parser<_,_> = fun stream -> Reply stream.Position </code></pre> and atttach position information to every bit you parse using <pre><code>position .>>. yourParser (*or tuple2 position yourParser*) </code></pre> position parser does not consume any input and thus it is safe to combine in that way. You can keep the code change required restricted to a single line and avoid uncontrollable code spread: <pre><code>type AST = Slash of int64 | Hash of int64 let slash : Parser<AST,_> = char '/' >>. pint64 |>> Slash let hash : Parser<AST,_> = char '#' >>. pint64 |>> Hash let ast : Parser<AST,_> = slash <|> hash (*if this is the final parser used for parsing lists of your ASTs*) let manyAst : Parser< AST list,_> = many (ast .>> spaces) let manyAstP : Parser<(Position * AST) list,_> = many ((position .>>. ast) .>> spaces) (*you can opt in to parse position information for every bit you parse just by modifiying only the combined parser *) </code></pre> Update: FParsec has a predefined parser for positions: <a href="http://www.quanttec.com/fparsec/reference/charparsers.html#members.getPosition" rel="nofollow">http://www.quanttec.com/fparsec/reference/charparsers.html#members.getPosition</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPosition information in fparsec
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCetin Sert
UserOwnerUserId
1. USCetin Sert
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPosition information in fparsec
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.