StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19138092
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-02T13:30:10.447
FavoriteCount
0
LastActivityDate
2013-10-02T13:30:10.447
LastEditDate
LastEditorUserId
0
OwnerUserId
349948
ParentId
19135160
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I would also agree that having too many attributes is probably a sign of insufficient abstraction, which is usually harder to develop & debug, and so changing your design is probably a good idea. But, you do have a gold badge, so you've obviously been around and (probably) know what you are doing, and might have a reason to do this. In that case, I think it's a good idea to split up the initialization by category like you suggested. The only suggestion I would have is to use _ on the sub-init functions to signal to a user they aren't intended for normal use i.e. <pre><code>class A: def __init__(self): self.member0 = "a" self.__init_other_stuff() def __init_other_stuff(self): self.member1 = "b" self.member2 = "c" </code></pre> etc. This also hides them from tab-completion in most consoles & editors. Your other choice is to make this class a subclass of multiple classes that implement part of the interface if you really need A to contain those items directly, i.e. do something like this: <pre><code>class Logger(object): def __init__(self): self.logparam = 1 class NetworkSource(object): def __init__(self): self.netparam = 2 class A(Logger, NetworkSource): def __init__(self): Logger.__init__(self) NetworkSource.__init__(self) In [2]: a = A() In [3]: a.<tab> a.logparam a.netparam </code></pre> Then it would get the functionality of both classes, while having a relatively short init. Multiple inheritance is conceptually a little more complicated though IMHO. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PObest practise to init member
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCorley Brigman
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. This table or related slice is empty.
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.