Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5842411
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T12:00:52+00:00 2026-05-22T12:00:52+00:00

I’ve been using a design pattern that after using the Entity Framework Profiler seems

  • 0

I’ve been using a design pattern that after using the Entity Framework Profiler seems like it might be quite foolish.

I’ve been extended my entity classes to have properties that are filtered views of a collection associated with that entity. Like this:

public IEnumerable<Member> ActiveMembers
{
    get
    {
        return Members.Where(t => t.LeftDate == null);
    }
}

As I’m mainly interested in members who have not left the club this property was very useful and seemed to make sense.

However from running the EF Profiler I now know that this often leads to N+1 problems. If I loop through the members and also want to show their address then each request for an address results in an extra db query.

I know from this question I asked that I could modify my property to:

return Members.CreateSourceQuery().Include("Address")
              .Where(t => t.LeftClubDate == null);

This would get rid of the N+1 problem in this case, but I don’t always want the address information and I might want to follow another navigation property from Member.

Ideally I want to be able to keep the flexibility of my filtered properties like ActiveMembers and be able to decide afterwards what properties to include in the query. Like this:

var membersToDisplay = ActiveMembers.Include("Address").ToList();

Is this possible, or do I need to rething my filtered properties idea?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T12:00:52+00:00Added an answer on May 22, 2026 at 12:00 pm

    No, it is not possible to call Include on IEnumerable. Include is feature of ObjectQuery / DbQuery. It is possible to call Include on IQueryable (with EFv4.1 or custom extension) but it still internally cast passed query to ObjectQuery or DbQuery and throws exception if cast cannot be done. You must redesign your application.

    I don’t always want the address
    information and I might want to follow
    another navigation property from
    Member.

    You have to fill data based on your current needs or live with N+1 problem. For example you can use separate linq query:

    var clubId = ActiveClub.Id;
    var members = (from member in context.Members.Include("Address")
                   where member.LeftDate == null and member.ClubId == clubId
                   select member).ToList();
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.