StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2353170
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-02-28T23:45:56.577
FavoriteCount
0
LastActivityDate
2010-03-01T00:22:32.247
LastEditDate
2010-03-01T00:22:32.247
LastEditorUserId
200266
OwnerUserId
200266
ParentId
2353140
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
I’ve not seen many of your <code>field_map</code>s in real life. I think that would only make sense if you were to use the <code>field_map</code> at some other place in your code as well. Concerning your third example: Even though you don’t need to assign to them (other than <code>None</code>), it is common practice to explicitly declare attributes in the <code>__init__</code> method, so you’ll easily see what properties your object has. So the following is better than simply having an empty <code>__init__</code> method (you’ll also get a higher pylint score for that): <pre><code>class Blah(object): def __init__(self): self.foo = None self.bar = None blah = Blah() blah.foo = var1 </code></pre> The problem with this approach is, that your object might be in a not well-defined state after initialisation, because you have not yet defined all of your object’s properties. This depends on your object’s logic (logic in code and in meaning) and how your object works. If it is the case however, I’d advise you not to do it this way. If your object relies on <code>foo</code> and <code>bar</code> to be meaningfully defined, you should really put them inside of your <code>__init__</code> method. If, however, the properties <code>foo</code> and <code>bar</code> are not mandatory, you’re free to define them afterwards. If readability of the argument lists is an issue for you: Use keyword arguments.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPython 3 object construction: which is the most Pythonic / the accepted way?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDebilski
UserOwnerUserId
1. USDebilski
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.