StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10728611
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-05-23T22:10:55.393
FavoriteCount
0
LastActivityDate
2012-06-13T12:06:56.477
LastEditDate
2012-06-13T12:06:56.477
LastEditorUserId
181772
OwnerUserId
181772
ParentId
10725322
PostTypeId
2
Score
28
ViewCount
0
LastEditorDisplayName
text
Body
i am pretty sure that the reason people "naturally" don't like this is because it makes the meaning of later arguments ambiguous, depending on the length of the interpolated series: <pre><code>def dangerbaby(a, b, *c): hug(a) kill(b) >>> dangerbaby('puppy', 'bug') killed bug >>> cuddles = ['puppy'] >>> dangerbaby(*cuddles, 'bug') killed bug >>> cuddles.append('kitten') >>> dangerbaby(*cuddles, 'bug') killed kitten </code></pre> you cannot tell from just looking at the last two calls to <code>dangerbaby</code> which one works as expected and which one kills little kitten fluffykins. of course, some of this uncertainty is also present when interpolating at the end. but the confusion is constrained to the interpolated sequence - it doesn't affect other arguments, like <code>bug</code>. [i made a quick search to see if i could find anything official. it seems that the * prefix for varags was <a href="http://www.python.org/search/hypermail/python-1993/0001.html" rel="noreferrer">introduced in python 0.9.8</a>. the previous syntax is <a href="http://www.python.org/search/hypermail/python-1992/0260.html" rel="noreferrer">discussed here</a> and the rules for how it worked were rather complex. since the addition of extra arguments "had to" happen at the end when there was no * marker it seems like that simply carried over. finally there's a <a href="http://www.python.org/search/hypermail/python-1992/0292.html" rel="noreferrer">mention here</a> of a long discussion on argument lists that was not by email.]
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSemantics of tuple unpacking in python
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USandrew cooke
UserOwnerUserId
1. USandrew cooke
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSemantics of tuple unpacking 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CO+1 I like this example :D
 singulars
 PostPostId
 PO
 UserUserId
 USjamylak

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.