[
https://issues.apache.org/jira/browse/IGNITE-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042694#comment-16042694
]
Pavel Tupitsyn commented on IGNITE-5451:
----------------------------------------
{{LeftOuterJoin}} sounds reasonable to me, certainly more readable than
{{GroupJoin}}.
However, I think we should implement {{GroupJoin}} support as well, because
that is what most users would expect. Also some people may be migrating their
queries.
> .NET: Improve outer joins in LINQ
> ---------------------------------
>
> Key: IGNITE-5451
> URL: https://issues.apache.org/jira/browse/IGNITE-5451
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Reporter: Pavel Tupitsyn
> Labels: .NET, LINQ
> Fix For: 2.2
>
>
> Currently outer joins are supported in a convoluted way, via a regular join
> with {{DefaultIfEmpty()}} call:
> {code}
> var res = persons.Join(roles.DefaultIfEmpty(),
> person => person.Value.RoleId, role => role.Key,...)
> {code}
> This is not consistent with LINQ to objects, Entity Framework and other
> things out there, and unexpected for the users.
> Instead we should support {{GroupJoin}} properly, see
> https://stackoverflow.com/questions/584820/how-do-you-perform-a-left-outer-join-using-linq-extension-methods
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
