StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3659916
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-09-07T15:10:34.540
FavoriteCount
0
LastActivityDate
2010-09-07T15:24:48.423
LastEditDate
2010-09-07T15:24:48.423
LastEditorUserId
398968
OwnerUserId
398968
ParentId
3659773
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Do not walk the filesystem (!) and scan the Python source code of the backends! That's an ugly hack at the best of times, and even worse here because you don't need anything like it at all! Registering all the classes on import is perfectly OK. <hr> Store the backends in a class attribute instead of an instance attribute; that way, all <code>Storage</code> instances will look at the same set of backends: <pre><code>>>> class Storage(object): ... backends = set() ... ... def register(self, backend): ... self.backends.add(backend) ... </code></pre> Every backend can register itself by instantiating its own <code>Storage</code>, which has access to the class-level <code>backends</code> attribute: <pre><code>>>> foo = Storage() >>> foo.register("text") >>> bar = Storage() >>> bar.register("xml") </code></pre> You can read this attribute by instantiating another <code>Storage</code>, which will read the same variable: <pre><code>>>> baz = Storage() >>> baz.backends {'xml', 'text'} </code></pre> <hr> You could even store the backend instances in a class attribute of <code>Connection</code>, and register each backend upon instantiation: <pre><code>>>> class Connection(object,metaclass=abc.ABCMeta): ... @abc.abstractmethod ... def register(self, backend): ... pass ... ... backends = set() ... >>> class TextBackend(Connection): ... def register(self): ... super().backends.add(self) ... ... def __init__(self): ... self.register() ... >>> class XMLBackend(Connection): ... def register(self): ... super().backends.add(self) ... ... def __init__(self): ... self.register() ... >>> foo = TextBackend() >>> bar = XMLBackend() >>> Connection.backends {<__main__.XMLBackend object at 0x027ADAB0>, \ <__main__.TextBackend object at 0x027ADA50>} </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPython Plugin-System - HOWTO
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USKatriel
UserOwnerUserId
1. USKatriel
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.