StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19735525
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-01T21:17:00.943
FavoriteCount
0
LastActivityDate
2013-11-01T21:17:00.943
LastEditDate
LastEditorUserId
0
OwnerUserId
908494
ParentId
19735281
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
First, since you didn't give an example, here's the familiar toy minimal class hierarchy: <pre><code>class Base(object): def __init__(self): print("I'm a base") class Child(Base): def __init__(self): super(Child, self).__init__() print("I'm also a child") </code></pre> Now, presumably you want to decide whether to be a <code>Child</code> or not in the middle of, or right after, <code>Base.__init__</code>. The best way to do that is to not do it; just move the choice earlier. Then you don't need to do any re-classing; you just construct the class you actually want, and know it's going to be initialized as appropriate for that class. You can either use a factory function: <pre><code>def basefactory(child=False): if child: return Child() else: return Base() </code></pre> … or an "alternate constructor" method: <pre><code>class Base(object): def __init__(self): print("I'm a base") @classmethod def make(cls, child=False): if child: return Child() else: return cls() </code></pre> Or a custom <code>__new__</code> method: <pre><code>class Base(object): def __init__(self): print("I'm a base") def __new__(cls, child=False): return super(Base, cls).__new__(Child if child else cls) </code></pre> The advantage of all of these mechanisms is that <code>__init__</code> works the way it's supposed to. If someone writes a normal, Pythonic <code>__init__</code> method that correctly calls its superclass, it won't get trapped in an endless loop. The only reason to re-<code>__class__</code> something in the base <code>__init__</code> would be if you wanted to explicitly prevent the child's <code>__init__</code> getting called. That's a very rare case, but if it's what you actually want, it's easy: <pre><code>class Base(object): def __init__(self, child=False): super(Base, self).__init__() if child: self.__class__ = Child </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCreate a subclass, instead, when calling the creation of a class, depending on some logic
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USabarnert
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. 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.