Jon

My feedback

  1. 214 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    This is something we can consider in EF Core if at some point we implement change tracking proxies.

    From the EF6 perspective we don’t plan to change the current behavior. An important part of the motivation to create change tracking proxies is to avoid the cost of performing data comparisons.

    Jon commented  · 

    Personally, I don't like the solution of having to use INotifyPropertyChanged. That means that you can't use auto properties for succinctness, thus massively increasing the size of your entity classes if you have a lot of properties. If you don't use that, then, it's using snapshot, which of course uses lots of memory and is slow. Previously, I found that code first was slower than EF 5. So, now you get to put tons more boiler plate code in your classes or, things are slower. I've given up on the idea of having EF work with anything except a very small number of objects. The sad thing is that I've had better success with other ORMs like Hibernate in this regard.

    Jon supported this idea  · 

Feedback and Knowledge Base