StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4794398
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2011-01-25T14:05:29.607
FavoriteCount
0
LastActivityDate
2011-02-25T07:32:07.960
LastEditDate
2011-02-25T07:32:07.960
LastEditorUserId
405143
OwnerUserId
405143
ParentId
4794375
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
<ol> <li>Setting <code>Ninja.prototype = Person.prototype;</code> is saying that all Ninjas are Persons, and all Persons are Ninjas, since it simply makes the two prototypes point to the same thing. So changing <code>Ninja.prototype</code> will change <code>Person.prototype</code> and vice versa.</li> <li>Setting <code>Ninja.prototype = new Person();</code> is saying that all Ninjas start off being a regular person, but <code>Ninja.prototype</code> can be modified without changing the definition of <code>Person</code>. The key here is the <code>new</code> keyword, which creates a unique instance of <code>Person</code>, and is therefore free to be modified without affecting anything else.</li> </ol> <hr> <h2>Example of <code>Ninja.prototype = Person.prototype</code></h2> Define <code>Ninja</code>'s prototype to be the same as Person's: <pre><code>function Person() {} Person.prototype.dance = function () {}; // A Person can dance function Ninja() Ninja.prototype = Person.prototype; // Now a Ninja can dance too! </code></pre> An instance of <code>Ninja</code> has the abilities of <code>Person</code>: <pre><code>var ninja = new Ninja(); ninja.dance(); </code></pre> But, modifications to the definition of <code>Ninja</code> also affect instances of <code>Person</code>: <pre><code>Ninja.prototype.kill = function () {}; // Oh no! Now a Person can kill too! var bob = new Person(); bob.kill(); // Not what we wanted... </code></pre> <hr> <h2>Example of <code>Ninja.prototype = new Person()</code></h2> Define <code>Person</code> in the same way as before: <pre><code>function Person(){}; Person.prototype.dance = function () {}; // A Person can dance </code></pre> Now I'll break <code>Ninja.prototype = new Person()</code> into two steps. First, create a new <code>Person</code>, called <code>defaultNinja</code>: <pre><code>var defaultNinja = new Person(); // Despite the name, it's just a regular Person </code></pre> Then define all <code>Ninja</code>s to be like the default: <pre><code>function Ninja(){}; Ninja.prototype = defaultNinja; // Really the same as Ninja.prototype = new Person(); </code></pre> This time if we change what <code>Ninja</code>s can do: <pre><code>Ninja.prototype.kill = function () {}; // OR, defaultNinja.kill = function () {}; </code></pre> Instances of <code>Person</code> aren't affected: <pre><code>ninja.kill(); // Now the ninja can kill var bob = new Person(); bob.kill(); // ERROR, because Person.prototype doesn't have kill(), // only defaultNinja does </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POQuestion regarding Inheritance in JavaScript
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDavid Tang
UserOwnerUserId
1. USDavid Tang
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POQuestion regarding Inheritance in JavaScript
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.