StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20508519
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-11T00:55:04.360
FavoriteCount
0
LastActivityDate
2013-12-11T01:07:11.847
LastEditDate
2013-12-11T01:07:11.847
LastEditorUserId
398212
OwnerUserId
398212
ParentId
20508106
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Here's a really bad way (undefined behavior), but I think it shows the path to a more reasonable technique. Your current namespace is really a dictionary under the covers: <pre><code>>>> local_namespace = locals() >>> name = "myVarName" >>> local_namespace[name] = 'VarData' >>> myVarName 'VarData' </code></pre> But that's not very DRY - you have to write the name of the variable twice! It would be nice to use a variable that stored the name of our dynamically created variable so we didn't have to type it twice: <pre><code>>>> name 'myVarName' </code></pre> obviously doesn't work for this. But we can use our dictionary again: <pre><code>>>> local_namespace[name] 'VarData' </code></pre> So now we can store and recall the value associated with our variable. But wait - there's no need to use the special <code>locals()</code> dictionary for this - an ordinary dictionary will do! <pre><code>>>> d = {} >>> d[name] = 'VarData' >>> d[name] 'VarData' </code></pre> And now we have all these added benefits, like being able to keep track of the names of several of these variables in a list: <pre><code>>>> l = [] >>> l.append('myVarName') >>> l.append('anotherVarName') </code></pre> Dictionaries even do this for us: <pre><code>>>> d['anotherVarName'] = 123 >>> d.keys() ['myVarName', 'anotherVarName'] </code></pre> Unless you're doing terrifically wacky things, it's hard to imagine how constructing variable names could be more useful than using a dictionary.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEquivalent of "genvarname" in Python
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USThomas
UserOwnerUserId
1. USThomas
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POEquivalent of "genvarname" 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
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.