Question

I’m working with LINQ and EF for the first time. I’ve designed a db that links a Developer entity with a SkillProfile entity via a many to many entity named “DeveloperMatchesProfile”.

The problem that I’m running into is that my LINQ query (which depends on using a navigational property off of the original range variable) needed an additional Where clause. This looks like it could turn inefficient quickly. Is there a better way? Does this construct pose a threat to performance?

Answer 1

Why not do something like this?

 var skills = _Context.DeveloperMatchesProfiles
      .Where(x => x.DeveloperId == developerId)
      .Select(x => x.SkillProfile);

You simply select the instances of DeveloperMatchProfiles with that developer Id and select the linked navigation property. You’re basically going backwards, if I understand your relationships correctly.