StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15597164
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-24T10:06:00.410
FavoriteCount
0
LastActivityDate
2015-01-27T10:30:01.660
LastEditDate
2015-01-27T10:30:01.660
LastEditorUserId
238902
OwnerUserId
1163867
ParentId
15595289
PostTypeId
2
Score
16
ViewCount
0
LastEditorDisplayName
text
Body
According to <a href="http://codeblog.jonskeet.uk/category/edulinq/" rel="noreferrer">eduLINQ</a>: <blockquote> The best way to get to grips with what GroupJoin does is to think of Join. There, the overall idea was that we looked through the "outer" input sequence, found all the matching items from the "inner" sequence (based on a key projection on each sequence) and then yielded pairs of matching elements. GroupJoin is similar, except that instead of yielding pairs of elements, it yields a single result for each "outer" item based on that item and the sequence of matching "inner" items. </blockquote> The only difference is in return statement: Join: <pre><code>var lookup = inner.ToLookup(innerKeySelector, comparer); foreach (var outerElement in outer) { var key = outerKeySelector(outerElement); foreach (var innerElement in lookup[key]) { yield return resultSelector(outerElement, innerElement); } } </code></pre> GroupJoin: <pre><code>var lookup = inner.ToLookup(innerKeySelector, comparer); foreach (var outerElement in outer) { var key = outerKeySelector(outerElement); yield return resultSelector(outerElement, lookup[key]); } </code></pre> Read more here: <ul> <li><a href="http://codeblog.jonskeet.uk/2010/12/31/reimplementing-linq-to-objects-part-19-join/" rel="noreferrer">Reimplementing LINQ to Objects: Part 19 - Join</a></li> <li><a href="http://codeblog.jonskeet.uk/2011/01/01/reimplementing-linq-to-objects-part-22-groupjoin/" rel="noreferrer">Reimplementing LINQ to Objects: Part 22 - GroupJoin</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLinq to Entities join vs groupjoin
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDefault
UserOwnerUserId
1. USMarcinJuraszek
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.