StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9933119
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-29T20:36:23.047
FavoriteCount
0
LastActivityDate
2012-03-29T20:36:23.047
LastEditDate
LastEditorUserId
0
OwnerUserId
227242
ParentId
9932913
PostTypeId
2
Score
13
ViewCount
0
LastEditorDisplayName
text
Body
In a <code>let</code> binding, the expression can have any type, and all you're doing is giving it a name (or pattern matching on its internal structure). In the <code><-</code> version, the expression must have type <code>m a</code>, where <code>m</code> is whatever monad the <code>do</code> block is in. So in the <code>IO</code> monad, for instance, bindings of this form must have some value of type <code>IO a</code> on the right-hand side. The <code>a</code> part (inside the monadic value) is what is bound to the pattern on the left-hand side. This lets you extract the "contents" of the monad within the limited scope of the <code>do</code> block. The <code>do</code> notation is, as you may have read, just syntactic sugar over the monadic binding operators (<code>>>=</code> and <code>>></code>). <code>x <- expression</code> de-sugars to <code>expression >>= \x -></code> and <code>expression</code> (by itself, without the <code><-</code>) de-sugars to <code>expression >></code>. This just gives a more convenient syntax for defining long chains of monadic computations, which otherwise tend to build up a rather impressive mass of nested lambdas. <code>let</code> bindings don't de-sugar at all, really. The only difference between <code>let</code> in a <code>do</code> block and <code>let</code> outside of a <code>do</code> block is that the <code>do</code> version doesn't require the <code>in</code> keyword to follow it; the names it binds are implicitly in scope for the rest of the <code>do</code> block.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO"<-" bindings in do notation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbitbucket
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.