You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/06/08 13:11:18 UTC
[jira] [Created] (IGNITE-5451) .NET: Improve outer joins in LINQ
Pavel Tupitsyn created IGNITE-5451:
--------------------------------------
Summary: .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
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)