EF4 save complex detached object graph

Question

I've got the following EntityObject-based EF model (properties written here as fields for keeping code cleaner):

Booking 
{
   int BookingID;
   EntityCollection<BookingCustomer> BookingCustomers;
   string Notes;
}

BookingCustomer 
{
   Customer Customer;
   Booking Booking;
   int CustomerID;
   int BookingID;
   string Notes;
}

Customer 
{
   int CustomerID;
   string Name;
}

I'm loading the object graph in a detached manner:

Booking existingBooking;
using(MyContext ctx = new MyContext())
{
    ctx.Bookings.MergeOption = MergeOption.NoTracking;
    ctx.BookingCustomers.MergeOption = MergeOption.NoTracking;
    ctx.Customers.MergeOption = MergeOption.NoTracking;
    existingBooking = ctx.Bookings
       .Include("BookingCustomers")
       .Include("BookingCustomers.Customer")
       .First();
}

Modifying booking and customer data:

existingBooking.Notes = "Modified";
existingBooking.BookingCustomers.First().Name += " Edited";

Saving it:

using(MyContext ctx = new MyContext())
{
        ctx.Bookings.Attach(existingBooking);
        ctx.ObjectStateManager.GetObjectStateEntry(existingBooking ).SetModified();
        ctx.Refresh(RefreshMode.ClientWins, existingBooking);    
        ctx.SaveChanges();
}

I get a new Customer record created (instead of existing record updated).

I've also tried this:

using(MyContext ctx = new MyContext())
{
    ctx.Customers.Attach(existingBooking.BookingCustomers.First());
    ctx.ObjectStateManager.GetObjectStateEntry(existingBooking.BookingCustomers.First()).SetModified();
    ctx.Refresh(RefreshMode.ClientWins, existingBooking.BookingCustomers.First());

    ctx.Bookings.Attach(existingBooking);
    ctx.ObjectStateManager.GetObjectStateEntry(existingBooking ).SetModified();
    ctx.Refresh(RefreshMode.ClientWins, existingBooking);    
    ctx.SaveChanges();
}

but getting exception on line ctx.Customers.Attach(existingBooking.BookingCustomers.First());:

System.InvalidOperationException: A referential integrity constraint violation occurred: The property values that define the referential constraints are not consistent between principal and dependent objects in the relationship.

How can i make it work?

I ended up using attached objects, so that the context is maintained from load to save. — Muxa, Apr 19 '12 at 04:24

score 1 · Answer 1 · edited May 23 '17 at 12:04

It is not about refreshing. If you modify the graph in detached state EF is not able to find what changes you did. You must manually set the state of each modified entity or relation. Attach will put whole graph in Unchanged state and ChangeObjectState affects only single entity in the graph.

You found that the easiest way is to load the whole graph again during saving and manually merge your changes to attached graph. Especially if you want to delete some relations / entities or do complex operations with many to many relation this would be handy.

score 1 · Answer 2 · answered Aug 04 '11 at 09:38

1

Ladislav is correct. However, there is one more option that you should consider which would solve this problem and still allow you to retain the detatched model - self tracking POCOs. There's a T4 template (it's either bundled with VS2010 or is available as a download) which allows an object graph to track its state (this includes adding / removing objects into the graph as well as what properties with an object have changed) so that you can reattach the graph having made modifications; EF4 will figure out the changes and apply those to object state manager for you.

answered Aug 04 '11 at 09:38

Isaac Abraham

3,422
2
23
26

I have tried the self-tracking POCOs, and got the same result actually - new customer was created every time i save a booking. – Muxa Aug 05 '11 at 00:37
something is not right. can you look at the object's state before attaching it to the object context - it should be marked as modified. – Isaac Abraham Aug 05 '11 at 23:25

EF4 save complex detached object graph

2 Answers2