Christopher Grace

My feedback

  1. 7 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      Christopher Grace supported this idea  · 
      Christopher Grace commented  · 

      I cannot believe this only has 11 votes! The use of LEFT OUTER JOINs instead of intended INNER JOINs seems to expand the generated SQL exponentially, and slow performance to a crawl.

      In the simple example above, it's not that bad. But more complex queries bring in many tables with nullable foreign keys. Join/Bridge tables also introduce LEFT OUTER JOINs. Oddly enough, sometimes the do not.

      When performance is an issue, and developers see the SQL generated, they invariably abandon LINQ for Stored Procedures and TSQL. At lease that has been my experience 100% of the time.

      I LOVE EF, and stubborly refused to give up. I burned days of my own time trying to understand how to control the JOINs. But I am plumb out of time and have to give up.

      See https://stackoverflow.com/questions/44753108/how-can-entity-framework-be-forced-to-generate-a-sql-inner-join-on-a-nullable-fo/44754529?noredirect=1#comment76500730_44754529

      Please, please add a JoinRequired, IncludeRequired, or any other means to let the developer choose the JOIN.

    Feedback and Knowledge Base