Cascade Delete and 1-to-1 (or 1-to-0..1) Relationships

re: Cascade Delete and 1-to-1 (or 1-to-0..1) Relationships

Daniel Simmons - MSFT — Fri, 01 Jul 2011 17:08:20 GMT

I haven't checked (I'm no longer part of the EF team), but I think it highly unlikely that this issue was addressed in EF 4.1 since that was a release that only added support for code-first development on top of the same core EF bits that are in EF 4.0--it didn't change the core EF DLLs. The next full release of the EF, though, (which I gather is now available as a CTP) may have fixed this issue.

You might want to ask on the EF forums to get confirmation one way or another of whether or not this issue is fixed in that CTP.

Good luck!

re: Cascade Delete and 1-to-1 (or 1-to-0..1) Relationships

Ravi Pathak — Fri, 01 Jul 2011 13:47:54 GMT

Hi Danny

Just wanted to know whether this workaround is needed with EF4.1 or is the root cause fixed?

Thanks

Ravi Pathak

re: Cascade Delete and 1-to-1 (or 1-to-0..1) Relationships

mdejonge — Wed, 17 Mar 2010 13:55:30 GMT

Hi Danny,

Thanks a lot for sharing this information.

For some reason the method EndIsPresentAndDeleted doesn't work for me. I had to change it into the following to make it work:

private bool EndIsPresentAndDeleted(ObjectStateEntry entry, int index) {

var key = entry.OriginalValues[index];

var stateEntry = ObjectStateManager.GetObjectStateEntries(EntityState.Deleted).FirstOrDefault(a => a.EntityKey == key);

return stateEntry != null;

}

Regards,

Merijn

re: Cascade Delete and 1-to-1 (or 1-to-0..1) Relationships

Daniel Simmons - MSFT — Sun, 14 Feb 2010 00:19:32 GMT

I'm glad that this has helped you. Unfortunately it looks like this won't be resolved in a built-in way for .net 4--the full fix is somewhat involved and just too much for how late we are in the product cycle. We'll get it for next time, though.

- Danny

re: Cascade Delete and 1-to-1 (or 1-to-0..1) Relationships

RobCannon — Sat, 13 Feb 2010 23:23:13 GMT

Thank you!

I ran into this issue but was unable to solve it until now. Also, I couldn't get this code to work directly either. But I was able to hard code the relationship that was troublesome for me into the code and everything works now. This was happening when I was trying to delete an entity via WCF Ria Services. Hopefully the issue will be resolved with .NET 4.0.