Sam Nelson

My feedback

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

    We’ll send you updates on this idea

    Sam Nelson commented  · 

    forgot to add the primary key constraints to those two tables, just in case it wasn't already obvious. Also, in the .NET side of things, because one entity a key for the other, it is implicit that the key entity A is included whenever querying a B. No need to explicity write .Include(b => b.Key).

    Sam Nelson shared this idea  · 
  2. 323 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Sam Nelson commented  · 

    lfbicalho mentioned using DI to control which implementation EF constructs. Possibly if no DI binding was made, a dynamic proxy class that implements the interface could work too?

    Sam Nelson supported this idea  · 
  3. 369 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Sam Nelson supported this idea  · 
  4. 30 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Sam Nelson supported this idea  · 
  5. 107 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Sam Nelson supported this idea  · 

Feedback and Knowledge Base