StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12397948
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-13T00:43:18.117
FavoriteCount
0
LastActivityDate
2012-09-24T14:27:23.007
LastEditDate
2012-09-24T14:27:23.007
LastEditorUserId
41655
OwnerUserId
41655
ParentId
12397712
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
The main con / gotcha with using class attributes to provide default values for what you intend to be instance-specific data is that the default values are going to be shared between all instances of the class until the value is changed. E.g.: <pre><code>class Foo(object): a = [] foo1 = Foo() foo2 = Foo() foo1.a.append(123) foo1.a # [123] foo2.a # [123] </code></pre> However, the following will work as one might expect: <pre><code>class Bar(object): a = 123 bar1 = Bar() bar2 = Bar() bar1.a = 456 bar2.a # 123 </code></pre> To avoid this gotcha while using this technique, you should only use it to set defaults that are immutable values. (E.g. numbers, strings, tuples…) The reason why Python behaves this way is that when you access an attribute with: <pre><code>foo.bar </code></pre> then <code>bar</code> is first looked up in the object <code>foo</code>. If the name in not found in the object (i.e. in <code>foo.__dict__</code>), then the name is looked up in the type of that object. For example, this mechanism is part of how method lookups work. (If you look at the <code>__dict__</code> of an object, you'll notice its methods aren't there.) Other minor issues are that this exposes the defaults through the type object when they're intended to be instance-specific; and that it mixes the definitions of class-specific attributes (like constants) if you have any with the defaults. The corollary of the former is that this will let you redefine the value of the default later on for all objects that haven't changed the value yet by assigning to the class attribute. (This could be useful, or confusing; the same precaution against mutable "global" variables applies.)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODefining a Python class with lots of attributes - style
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmillimoose
UserOwnerUserId
1. USmillimoose
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODefining a Python class with lots of attributes - style
 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.