StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7039255
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-12T11:11:10.150
FavoriteCount
0
LastActivityDate
2011-08-12T11:11:10.150
LastEditDate
LastEditorUserId
0
OwnerUserId
135778
ParentId
7038730
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
billy moon shows a good start, but the problem with using object literals, is that you cannot cross reference other fields/functions/properties. I much prefer the revealing module pattern (see <a href="http://www.wait-till-i.com/2007/08/22/again-with-the-module-pattern-reveal-something-to-the-world/" rel="nofollow">http://www.wait-till-i.com/2007/08/22/again-with-the-module-pattern-reveal-something-to-the-world/</a>) the revealing module pattern combines a self-executing function, an exploitation (of sorts) of closures to provide internal private functions/fields, and allows you to pass params to initialise your namespaced object. <pre><code>var namespacedObject = function(param) { var settings = param || someDefaultSetting, //default if no param supplied somePrivateField = "someValue", somePublicField = "i'm public"; //define some method we will later make public function toggleComments(){ $("comments-section").hide(); $("comments-button").click(function (){ $(this).value= somePrivateField; return false; }); } //this is where the magic happens, //return object with all public fields/functions return { toggleComments : toggleComments, somePublicField : somePublicField }; }(someParam); </code></pre> You can see that the namespaced object contains a private field <code>somePrivateField</code>, which can be referenced from publicly accessible methods. Also, notice i have exposed a public field, and accepted some params which i may use/reference in functions etc (and you can default it to some default if nothing is passed in. can be used like this: <pre><code>namespacedObject.toggleComments(); alert(namespacedObject.somePublicField); alert(namespacedObject.somePrivateField); //undefined - it's private of course! </code></pre> one reason i like this is that it's very easy to see what is public/private by just glancing at the object literal returned from the self-executing function Hope that's helpful
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJavascript converting to namespace and calling functions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USWickyNilliams
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POJavascript converting to namespace and calling functions
 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
 VTAcceptedByOriginator
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.