StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16531652
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-13T21:42:47.877
FavoriteCount
0
LastActivityDate
2013-05-13T21:50:07.793
LastEditDate
2013-05-13T21:50:07.793
LastEditorUserId
558823
OwnerUserId
558823
ParentId
16530466
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
You can easily build a custom combinator or parser that validates parsed input. If you only want to use combinators ("Haskell-style"), you could use <pre><code>let pDateString = pstring "1/2/2000" let pDate1 = pDateString >>= fun str -> try preturn (System.DateTime.Parse(str)) with _ -> fail "Date format error" </code></pre> as Guvante just proposed. If you want to avoid construction temporary parsers (see <code>preturn ...</code> and <code>pfail ...</code> above), you can just let the function accept a second parameter and directly return <code>Reply</code> values: <pre><code>let pDate2 = pDateString >>= fun str stream -> try Reply(System.DateTime.Parse(str)) with _ -> Reply(Error, messageError "Date format error") </code></pre> If you want the error location to be at the beginning of the malformed date string, you could replace <code>>>=</code> with <code>>>=?</code>. Note that this also has consequences for error recovery. If you want to have full control, you can write the parser only using the lower level API, starting with a basic version like the following: <pre><code>let pDate3 = fun stream -> let reply = pDateString stream if reply.Status = Ok then try Reply(System.DateTime.Parse(reply.Result)) with _ -> Reply(Error, messageError "Date format error") else Reply(reply.Status, reply.Error) </code></pre> This last version would also allow you to replace the pDateString parser with code that directly accesses the CharStream interface, which could give you some additional flexibility or performance.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POParsing date and time with FParsec
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USStephan Tolksdorf
UserOwnerUserId
1. USStephan Tolksdorf
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POParsing date and time with 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
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.