Ernesto

My feedback

  1. 4 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ernesto shared this idea  · 
  2. 117 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ernesto supported this idea  · 
    Ernesto commented  · 

    I totally agree. Also, if you have multiple 1-N relationships in a single query using current Include() implementation, the resulting query is huge and so is the result set. Performance obviously decreases as to be unacceptable.
    Most of the times you have to Load (or LoadProperty) what takes additional roundtrips.
    Nowadays there's not optimal resolution to this problem using pure EF. Developers have to load objects manually using stored procedures.

    What you're proposing is completely reasonable and it amazes me how this wasn't a design issue from the first version of EF, since it affects performance so much.

Feedback and Knowledge Base