StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14094498
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-12-30T20:46:43.333
FavoriteCount
0
LastActivityDate
2012-12-30T20:52:32.837
LastEditDate
2012-12-30T20:52:32.837
LastEditorUserId
1936075
OwnerUserId
1936075
ParentId
14094378
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Python does not really distinguish "public" from "private" variables. Anything you assign to a name in self using 'self.something = value' will be an instance variable for that instance. Python does have two conventions that are relevant here: 1) Python fields or methods are prefixed with underscores('_') to tell users 'this is not a concern outside this class'. A single underscore is a conventional way of identifying more or less what a language like C# would call a 'protected' variable: it's internal to the implementation and should be left alone except by this class and derived classes. A double underscore is like a C# 'private' variable: it's internal and should be left alone even by derived classes, it can't be overridden <pre><code>class Example(object): def __init__(self) self._protected= "protected" self.__private = "private" self.public = "public" class Derived(Example): pass d = Derived() print d._protected >> protected print d.__private >> AttributeError: 'Derived' object has no attribute '__private' </code></pre> Strictly speaking the single underscore is just a typographical convention. The double underscore does actually mangle the name inside the class to prevent inheritance. 2) You example is potentially case for using the property decorator if AnotherClass is actually going to hang around, and if manipulating the AnotherClass instance affects the state of AnotherClass. <pre><code>class C: def __init__(self, parent = None): super(C, self).__init__(parent) self._private = AnotherClass() @property def public(self): return self._private.some_method_on_AnotherClass() @public.setter def set_pub(self, val) self._private.set_value_on_AnotherClass(val) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POShould I use "self" to define variables / objects of class instanced which I will not need to reach from the outside?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UStheodox
UserOwnerUserId
1. UStheodox
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
CommentsPostId
1. COThank you @theodox. This will help a lot of people. Great answer.
 singulars
 PostPostId
 PO
 UserUserId
 USPhil

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.