StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2875266
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-05-20T15:30:45.937
FavoriteCount
0
LastActivityDate
2016-08-23T09:56:46.643
LastEditDate
2016-08-23T09:56:46.643
LastEditorUserId
136246
OwnerUserId
136246
ParentId
2874566
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
I don't really know what you are trying to do here - all the code you posted works on instance variables. Instance variables are per-object, not per class, so I don't know what you mean when you say "I need a value from the parent class". There are several things that I note with your code: <ul> <li>Base classes should never be aware of subclasses. So creating <code>B</code> objects in <code>A#initialize</code> is not a good thing, because the base uses the subclass. </li> <li>You are overwriting the class <code>B#initialize</code> with a completely different behaviour than <code>A#initialize</code>. <s>You even change the parameter list. Not a very good thing either.</s> An object of a subclass should behave in the same way as an object of its superclass.</li> <li>When you call <code>B.new('myname')</code> the variable <code>@name</code> is never assigned, because the <code>A#initialize</code> method is never called. You will have to either call <code>super(:name => name)</code> (to run the superclass <code>initialize</code>) or you have to assign to <code>@name</code> directly in <code>B#initialize</code></li> <li>Once <code>@name</code> is defined, all your instance methods can use its value. Including the ones that are defined in the parent/superclass. </li> </ul> Let me say I'm not quite sure why you are using inheritance here, I have the feeling that it is not what you want. If you have two classes for two different things, there should never be inheritance involved. If you want to re-use code, either have a look at Ruby's mixin feature, or compose your complex objects of several "smaller" objects that have the behaviour you want to re-use.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAccess parent class instance variable
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USaverell
UserOwnerUserId
1. USaverell
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAccess parent class instance variable
 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
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.