StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1634679
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-10-28T01:22:24.493
FavoriteCount
0
LastActivityDate
2009-10-28T01:22:24.493
LastEditDate
LastEditorUserId
0
OwnerUserId
165216
ParentId
1632304
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
Here is a little wrapper class for FooB's to mimic FooA's, but still retain their FooB-ishness. <pre><code>from collections import namedtuple # use namedtuple to define some simple classes (requires Py2.6 or later) FooA = namedtuple('FooA', 'id name type foo') FooB = namedtuple('FooB', 'idfoo namefoo spam') # create a wrapper class for FooB's to look like a FooA class FooAMimic(object): attrMap = dict(zip(FooA._fields, FooB._fields)) # or if the fields aren't nicely ordered, declare this mapping explicitly #~ attrMap = { 'id' : 'idfoo', 'name' : 'namefoo', 'foo' : 'spam' } def __init__(self, obj): self.obj = obj def __getattr__(self, aname): ob = self.obj if aname in self.attrMap: return getattr(ob, self.attrMap[aname]) elif hasattr(ob, aname): return getattr(ob, aname) else: raise AttributeError("no such attribute " + aname) def __dir__(self): return sorted(set(dir(super(FooAMimic,self)) + dir(self.obj) + list(FooA._fields))) </code></pre> Use it like this: <pre><code># make some objects, some FooA, some FooB fa = FooA('a', 'b', 'c','d') fb = FooB('xx', 'yy', 'zz') fc = FooA('e', 'f', 'g','h') # create list of items that are FooA's, or FooA lookalikes coll = [fa, FooAMimic(fb), fc] # access objects like FooA's, but notice that the wrapped FooB # attributes are still available too for f in sorted(coll, key=lambda k : k.id): print f.id, '=', try: print f.namefoo, "(really a namefoo)" except AttributeError: print f.name </code></pre> Prints: <pre><code>a = b e = f xx = yy (really a namefoo) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBest way to construct a "complex" data structure in Python
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPaulMcG
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBest way to construct a "complex" data structure in Python
 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.