StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8344331
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-12-01T16:01:17.587
FavoriteCount
0
LastActivityDate
2011-12-02T00:27:41.463
LastEditDate
2011-12-02T00:27:41.463
LastEditorUserId
22364
OwnerUserId
22364
ParentId
8343986
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<code>FIRST(X)</code> = the terminals which can appear first when trying parse the non-terminal <code>X</code>. If it can match an empty string, epsilon is also included. <code>FOLLOW(X)</code> = the terminals which can appear immediately after the non-terminal <code>X</code>. This is a union of the FIRST-sets of all symbols appearing after <code>X</code> in any parsing rule. Read more: <a href="http://en.wikipedia.org/wiki/LL_parser" rel="nofollow">LL parser</a> The clues given are: <ol> <li><code>FIRST(A)</code>, <code>FIRST(S)</code> ⇒ All of the derivations of <code>A</code> and <code>S</code> respectively, must either begin with the terminal <code>b</code>, or be zero-length. <blockquote> <code>S</code> → <code>b</code> ... | ε <code>A</code> → <code>b</code> ... | ε </blockquote></li> <li><code>FOLLOW(S)</code> ⇒ There must be some construction where <code>S</code> is followed by the terminal <code>a</code>, or a non-terminal which can begin with <code>a</code>. (Neither <code>A</code> nor <code>S</code> qualify). <blockquote> <code>S</code> → <code>b</code> <code>S</code> <code>a</code> | ε <code>A</code> → <code>b</code> ... | ε </blockquote></li> <li><code>FOLLOW(A)</code> ⇒ There must be some construction where <code>A</code> is followed by each of the terminals <code>a</code> and <code>b</code>, or some non-terminal which can begin with those. <blockquote> <code>S</code> → <code>b</code> <code>S</code> <code>a</code> | ε <code>A</code> → <code>b</code> <code>A</code> <code>b</code> | <code>b</code> <code>A</code> <code>a</code> | ε </blockquote></li> <li><code>FOLLOW(A)</code> ⇒ Assuming <code>S</code> is the start-symbol, <code>A</code> must appear at the end of some branch of <code>S</code>, possibly followed by other nullable non-terminals. <blockquote> <code>S</code> → <code>b</code> <code>S</code> <code>a</code> | <code>A</code> | ε <code>A</code> → <code>b</code> <code>A</code> <code>b</code> | <code>b</code> <code>A</code> <code>a</code> | ε </blockquote> (NB. Adding <code>A</code> to <code>S</code> did not break the constraint on <code>FIRST(S)</code>)</li> </ol> We can make the grammar a little smaller: <blockquote> <code>S</code> → <code>b</code> <code>S</code> <code>a</code> | <code>A</code> | ε <code>A</code> → <code>b</code> <code>A</code> <code>b</code> | ε </blockquote> We can no longer generate strings like "<code>bbbabb</code>", but it does not violate the constraints.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFirst & Follow, Arithmetic Expressions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMarkus Jarderot
UserOwnerUserId
1. USMarkus Jarderot
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFirst & Follow, Arithmetic Expressions
 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
CommentsPostId
1. COYou right, FIRST(A) appeared twice, i made correction. I need to make the simplest grammar created by these groups. example: A->b | epsilon....
 singulars
 PostPostId
 PO
 UserUserId
 USDim

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.