StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19100004
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-30T17:14:36.063
FavoriteCount
0
LastActivityDate
2013-09-30T17:30:02.870
LastEditDate
2013-09-30T17:30:02.870
LastEditorUserId
846892
OwnerUserId
846892
ParentId
19099978
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
In py2.x you can return anything you want, but in py3.x you'll get errors if you return different types of values(objects) because you can't compare two different type of objects in py3.x <a href="http://docs.python.org/2/reference/expressions.html#not-in" rel="nofollow">Docs:</a>(py2.x): <blockquote> The operators <code><</code>, <code>></code>, <code>==</code>, <code>>=</code>, <code><=</code>, and <code>!=</code> compare the values of two objects. The objects need not have the same type. If both are numbers, they are converted to a common type. Otherwise, objects of different types always compare unequal, and are ordered consistently but arbitrarily. In the future, the comparison rules for objects of different types are likely to change. </blockquote> Py2.x: <pre><code>>>> x = [1, '2', [3]] >>> x.sort() >>> x [1, [3], '2'] </code></pre> Py3.x: <pre><code>>>> x = [1, '2', [3]] >>> x.sort() Traceback (most recent call last): x.sort() TypeError: unorderable types: str() < int() </code></pre> <a href="http://docs.python.org/3.0/whatsnew/3.0.html#ordering-comparisons" rel="nofollow">What's new in python3</a>: <blockquote> The ordering comparison operators (<code><</code>, <code><=</code>, <code>>=</code>, <code>></code>) raise a <code>TypeError</code> exception when the operands don’t have a meaningful natural ordering. Thus, expressions like <code>1 < ''</code>, <code>0 > None</code> or <code>len <= len</code> are no longer valid, and e.g. <code>None < None</code> raises <code>TypeError</code> instead of returning <code>False</code>. A corollary is that sorting a heterogeneous list no longer makes sense – all the elements must be comparable to each other. Note that this does not apply to the <code>==</code> and <code>!=</code> operators: objects of different incomparable types always compare unequal to each other. </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat should the type of the return value of the key function in sort() be?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAshwini Chaudhary
UserOwnerUserId
1. USAshwini Chaudhary
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
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.