It is a fairly common when developing a web application to materialize a complex object graph from Entity Framework to render a CRUD view, and then on a subsequent HTTP request write that object graph back to the database.
Apparently, that scenario is not well supported in Entity Framework. For a detailed discussion, see
http://stackoverflow.com/q/3635071/141172 NHibernate does support this
http://www.ienablemuch.com/2011/01/nhibernate-saves-your-whole-object.html There is at least one open source project that aims to solve this issue for EF:
http://stackoverflow.com/a/13820802/141172 I propose that Entity Framework should support a merge of disconnected object graph changes out of the box.
Apparently, that scenario is not well supported in Entity Framework. For a detailed discussion, see
http://stackoverflow.com/q/3635071/141172 NHibernate does support this
http://www.ienablemuch.com/2011/01/nhibernate-saves-your-whole-object.html There is at least one open source project that aims to solve this issue for EF:
http://stackoverflow.com/a/13820802/141172 I propose that Entity Framework should support a merge of disconnected object graph changes out of the box.