StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3384160
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-08-01T23:33:24.193
FavoriteCount
0
LastActivityDate
2010-08-01T23:33:24.193
LastEditDate
LastEditorUserId
0
OwnerUserId
95810
ParentId
3384010
PostTypeId
2
Score
19
ViewCount
0
LastEditorDisplayName
text
Body
Instead of: <pre><code> i=0 end=20 last_id=0 data=[] while(i<=end): i = i + 1 ... </code></pre> code: <pre><code> last_id=0 data=[] for i in xrange(1, 22): ... </code></pre> Same semantics, more compact and Pythonic. Instead of <pre><code>if not last or last == None: </code></pre> do just <pre><code>if not last: </code></pre> since <code>None</code> is false-ish anyway (so <code>not last</code> is <code>True</code> when <code>last</code> is <code>None). In general, when you want to check if something is</code>None<code>, code</code>is None<code>, not</code>== None`. In <pre><code> if(j['id'] <> last_id): </code></pre> lose the redundant parentheses and the obsolete <code><></code> operator and code instead <pre><code> if j['id'] != last_id: </code></pre> and also remove the redundant parentheses from other <code>if</code> statements. Instead of: <pre><code> if len(data) == 0: </code></pre> code: <pre><code> if not data: </code></pre> since any empty container is false-ish. In <pre><code>hash_str = str(hash.hexdigest()) </code></pre> code instead <pre><code>hash_str = hash.hexdigest() </code></pre> since the method already returns a string, making the <code>str</code> call redundant. Instead of: <pre><code> for item in data: writer.writerow(item) </code></pre> use <pre><code> writer.writerows(data) </code></pre> which does the loop on your behalf. Instead of <pre><code> ofile = open('tmp/'+file_name, mode='ab') ... ofile.close() </code></pre> use (in Python 2.6 or better, or in 2.5 by starting the module with <pre><code> from __future__ import with_statement </code></pre> to "import from the future" the <code>with</code> statement feature): <pre><code> with open('tmp/'+file_name, mode='ab') as ofile: ... </code></pre> which guarantees to do the close for you (including in cases where an exception might be raised). Instead of <pre><code>print "Upload Error: "+uploadr[0] </code></pre> use <pre><code>print "Upload Error:", uploadr[0] </code></pre> and similarly for other <code>print</code> statements -- the comma inserts a space for you. I'm sure there are more such little things, but these are a few that "jumped to the eye" as I was scanning your code.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLearning Python; How can I make this more Pythonic?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAlex Martelli
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POLearning Python; How can I make this more Pythonic?
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COawesome, thanks :)
 singulars
 PostPostId
 PO
 UserUserId
 USJayrox

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.