StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19800594
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-05T22:46:31.400
FavoriteCount
0
LastActivityDate
2013-11-05T23:02:47.597
LastEditDate
2013-11-05T23:02:47.597
LastEditorUserId
247623
OwnerUserId
247623
ParentId
19800454
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<a href="http://docs.python.org/2/library/itertools.html#itertools.groupby" rel="nofollow"><code>itertools.groupby</code></a> with some additional processing of what it outputs will do the job: <pre><code>from itertools import groupby data = { ('9', '0000022', 'LRA'), ('45', '0000016', 'PBM'), ('16', '0000048', 'PBL'), ... } def group_by_name_and_id(s): grouped = groupby(sorted(s), key=lambda (name, id_, type_): (name_, id)) for (name, id_), items in grouped: types = tuple(type_ for _, _, type_ in items) if len(types) > 1: yield (name, id_) + types print '\n'.join(str(x) for x in group_by_name_and_id(data)) </code></pre> outputs: <pre><code>('10', '0000007', 'PBM', 'IBL') ('12', '0000051', 'LRA', 'PBL') ('7', '0000014', 'LRA', 'PBL', 'IBL') ('9', '0000022', 'LRA', 'PBL', 'IBL') </code></pre> P.S. but I don't really like that design: thet types could/should really be a list contained in the 3rd item of the tuple, not part of the tuple itself... because this way the tuple is dynamic in length, and that's ugly... tuples aren't meant to be used like that. So best to replace <pre><code> types = tuple(type_ for _, _, type_ in items) yield (name, id_) + types </code></pre> with <pre><code> types = [type_ for _, _, type_ in items] yield (name, id_, types) </code></pre> yielding the much cleaner looking <pre><code>('10', '0000007', ['IBL', 'PBM']) ('12', '0000051', ['LRA', 'PBL']) ('7', '0000014', ['IBL', 'LRA', 'PBL']) ('9', '0000022', ['IBL', 'LRA', 'PBL']) </code></pre> for example then you can just iterate over the resulting data with <code>for name, id, types in transformed_data:</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POprocessing a set of unique tuples
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USErik Allik
UserOwnerUserId
1. USErik Allik
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POprocessing a set of unique tuples
 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
 VTUndeletion
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. 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.