StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8561258
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-19T12:18:59.837
FavoriteCount
0
LastActivityDate
2011-12-19T13:29:58.617
LastEditDate
2011-12-19T13:29:58.617
LastEditorUserId
400547
OwnerUserId
400547
ParentId
8560884
PostTypeId
2
Score
15
ViewCount
0
LastEditorDisplayName
text
Body
rich.okelly and Ladislav Mrnka are both correct in different ways. Both their answers deal with the fact that the <code>IEqualityComparer<T></code>'s methods won't be translated to SQL. I think it's worth looking at the pros and cons of each, which will take a bit more than a comment. rich's approach re-writes the query to a different query with the same ultimate result. Their code should result in more or less how you would efficiently do this with hand-coded SQL. Ladislav's pulls it out of the database at the point before the distinct, and then an in-memory approach will work. Since the database is great at doing the sort of grouping and filtering rich's depends upon, it will likely be the most performant in this case. You could though find that the complexity of what's going on prior to this grouping is such that Linq-to-entities doesn't nicely generate a single query but rather produces a bunch of queries and then does some of the work in-memory, which could be pretty nasty. Generally grouping is more expensive than distinct on in-memory cases (especially if you bring it into memory with <code>AsList()</code> rather than <code>AsEnumerable()</code>). So if either you were already going to bring it into memory at this stage due to some other requirement, it would be more performant. It would also be the only choice if your equality definition was something that didn't relate well to what is available just in the database, and of course it allows you to switch equality definitions if you wanted to do so based on an <code>IEqualityComparer<T></code> passed as a parameter. In all, rich's is the answer I'd say would be most-likely to be the best choice here, but the different pros and cons to Ladislav's compared to rich's makes it also well worth studying and considering.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to implement IEqualityComparer to return distinct values?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJon Hanna
UserOwnerUserId
1. USJon Hanna
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
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.