StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19057737
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-27T18:33:36.417
FavoriteCount
0
LastActivityDate
2013-09-27T18:33:36.417
LastEditDate
LastEditorUserId
0
OwnerUserId
2464386
ParentId
19057497
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
You can access A's version of <code>x</code> like this: <pre><code>((A)this).x </code></pre> as long as <code>x</code> wasn't declared <code>private</code> in class <code>A</code>. I've just tested it. Note that for fields, there is no overriding (as there is for methods). Thus, for an object of class C, there will be three <code>x</code> fields, but two of them can't be accessed normally because they are hidden by the other field named <code>x</code>. But casting the object as above will allow you to get at it, if it would have been visible if not hidden. I think it is very poor practice to declare fields of the same name in a class and its subclasses. It's confusing. It can happen legitimately if, say, you have a class <code>A</code> and you later change the implementation of <code>A</code> and add a new private field <code>z</code>; in that case, it may not be possible to make sure no subclasses of <code>A</code> already have a field <code>z</code>, since you don't even always know what all the subclasses are (if <code>A</code> is a class you've distributed publicly, for instance). I think it's for that reason that Java allows you to have fields of the same name, and why the hiding rules are the way they are, because it allows things like this to work without breaking all the other subclasses. Other than that, though, I recommend not having fields of the same name in superclasses and subclasses. Perhaps if they're all <code>private</code> it might be OK, though. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhow can I change variables in super class
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USajb
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
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
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.