I have 3 classes and trying to use LINQ methods
to perform an INNER JOIN
and a LEFT JOIN
. I'm able to perform each separately, but no luck together since I can't even figure out the syntax.
Ultimately, the SQL I'd write would be:
SELECT *
FROM [Group] AS [g]
INNER JOIN [Section] AS [s] ON [s].[GroupId] = [g].[Id]
LEFT OUTER JOIN [Course] AS [c] ON [c].[SectionId] = [s].[Id]
Classes
public class Group {
public int Id { get; set; }
public int Name { get; set; }
public bool IsActive { get; set; }
public ICollection<Section> Sections { get; set; }
}
public class Section {
public int Id { get; set; }
public int Name { get; set; }
public int GroupId { get; set; }
public Group Group { get; set; }
public bool IsActive { get; set; }
public ICollection<Course> Courses { get; set; }
}
public class Course {
public int Id { get; set; }
public int UserId { get; set; }
public int Name { get; set; }
public int SectionId { get; set; }
public bool IsActive { get; set; }
}
Samples
I want the result to be of type Group
. I successfully performed the LEFT JOIN
between Section
and Course
, but then I have an object of type IQueryable<
a>, which is not what I want, since
Group`.
var result = db.Section
.GroupJoin(db.Course,
s => s.Id,
c => c.SectionId,
(s, c) => new { s, c = c.DefaultIfEmpty() })
.SelectMany(s => s.c.Select(c => new { s = s.s, c }));
I also tried this, but returns NULL
because this performs an INNER JOIN
on all tables, and the user has not entered any Courses
.
var result = db.Groups
.Where(g => g.IsActive)
.Include(g => g.Sections)
.Include(g => g.Sections.Select(s => s.Courses))
.Where(g => g.Sections.Any(s => s.IsActive && s.Courses.Any(c => c.UserId == _userId && c.IsActive)))
.ToList();
Question
How can I perform an INNER
and a LEFT JOIN
with the least number of calls to the database and get a result of type Group
?
Desired Result
I would like to have 1 object of type Group
, but only as long as a Group
has a Section
. I also want to return the Courses
the user has for the specific Section
or return NULL
.
virtual
on all my properties), which is why my initial sample code uses.Include(...)
to fetch them right away. Does that affect your answer? – Lizarraga