StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16531381
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-13T21:23:48.147
FavoriteCount
0
LastActivityDate
2013-05-13T21:23:48.147
LastEditDate
LastEditorUserId
0
OwnerUserId
16800
ParentId
16530466
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> Is there a combinator for "post processing" a parser result </blockquote> It depends on what you want to do if you fail. You can always do <code>|>></code> to get your <code>DateTime</code> out. Failing it is equally interesting, I think your example could be (given a parser <code>sp</code> that gets the correct string, note it would be of type <code>Parser<string,'u></code>) <pre><code>sp >>= (fun s -> match DateTime.TryParse s with | true,result -> preturn result | false,_ -> fail) </code></pre> Here I am taking in the resultant string and calling the <code>TryParse</code> method, and returning either a <code>preturn</code> or a <code>fail</code> depending on whether it succeeds. I couldn't find any of the methods that worked exactly like that. Note that <code>>>=?</code> would cause a backtrack if it failed. <blockquote> Is it possible to apply a predicate to a string (as satisfy does for char)? </blockquote> You would have to call the predicate for every character (<code>2</code>, <code>20</code>, <code>201</code>) which is usually not ideal. I am pretty sure you could whip up something like this if you wanted, but I don't think it is ideal for that reason, not to mention handling partial matches becomes harder. <blockquote> Is there a better approach for parsing date/time? </blockquote> The biggest factor is "What do you know about the date/time?" If you know it is in that syntax exactly then you should be able to use a post process and be fine (since hopefully the error case will be rare) If you aren't sure, for instance if <code>PM</code> is optional, but would be unambiguously detailed, then you will probably want to break up the definition and combine it at the end. Note that here I have relaxed the character counts a little, you could add some <code>opt</code> to get even more relaxed, or replace the <code>pint32</code> with <code>digit</code> and manual conversions. <pre><code>let pipe6 = //Implementation left as an exercise let dash = skipChar '-' let space = skipChar ' ' let colon = skipChar ':' pipe6 (pint32 .>> dash) //Year (pint32 .>> dash) //Month (pint32 .>> space) //Day (pint32 .>> colon) //Hour (pint32 .>> space) //Minute (anyString) //AM/PM (fun year month day hour minute amPm -> DateTime(year, month, day, hour + (if amPm.Equals("PM", StringComparison.InvariantCultureIgnoreCase) then 12 else 0), minute, 0)) //No seconds </code></pre> Writing all that out I am not sure if you are better or worse off...
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. This table or related slice is empty.
UserOwnerUserId
1. USGuvante
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.