StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14374691
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-17T08:16:11.843
FavoriteCount
0
LastActivityDate
2013-01-17T14:17:25.150
LastEditDate
2013-01-17T14:17:25.150
LastEditorUserId
1047823
OwnerUserId
0
ParentId
14374645
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
It is a <a href="http://es5.github.com/#x13" rel="nofollow">Function Expression</a>2 Function Expressions can have names as well; the names of Function Expressions are only in scope in the function body1. (Since ECMAScript 5th edition deprecates <code>arguments.callee</code>, this is the only simple way to write a recursive "anonymous" function.) Because it is a Function Expression, the name may not1 introduce a new binding in the outer scope. Also, all functions are objects in JavaScript. In <code>f(..)</code>, <code>f</code> is evaluated before it is "invoked" with <code>(..)</code>; if <code>f</code> did not evaluate to a function then an error is thrown. This is why callbacks, which are just functions, can be named by variables and passed as parameters. Also, check the assumption/assertion about the prototype: <pre><code>var abc = function def() {} abc.prototype === abc // -> false abc.name // -> "def" </code></pre> <hr> 1 See Bergi's answer. 2 How to easily tell which is which? The grammar rules only allow <code>function ..</code> to be parsed as a Function Declaration when it is a <a href="http://es5.github.com/#x14" rel="nofollow">SourceElement</a> although most engines will still [incorrectly] parse a Function Declaration as a <a href="http://es5.github.com/#x12" rel="nofollow">Statement</a>. SourceElement productions only occur at the top-level "block" of a Program or the top-level "block" of a Function. In any case, whenever there is a <code>function ..</code> that appears in a place that requires an <a href="http://es5.github.com/#x11" rel="nofollow">Expression</a>, it will be parsed as a Function Expression. Examples that are all parsed as Function Expressions: <pre><code>// Can only assign values: Statements do not have values! var f = function () {} var g = function gName () {} // see Bergi's answer // Can only pass values: Statements do not have values! doIt(function () {}) // callback / "anonymous function" // IIFE: Immediately-Invoked Function Expression ;(function () {})() // standard IIFE ;(function () {} ()) // alternative standard IIFE ;+function () {} () // curious way to write an IIFE // basically you can use any unary operator to turn it into an expression not only // + but also - ! ~ and so on which will modify the return value accordingly </code></pre> The point is that in every single one of the above cases, <code>function ..</code> appears at a grammar location requiring an Expression and is thus parsed as a Function Expression. (The semicolons at the start of the lines above avoid "ambiguity" with ASI, which is required when writing in a semicolon-free style like I prefer.) However. <code>;function () {} ()</code> and <code>;function f () {} ()</code> are both invalid syntax - why? ;-)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POKnow JavaScript Function Expression vs Function Declaration, but what is this? Named Function Expression?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USChristoph
UserOwnerUserId
1. This table or related slice is empty.
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
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.