Entity Framework Concurrency Mode=Fixed causes related Entities to be saved - by HugeHugh

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 633479 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/27/2010 1:18:18 PM
Access Restriction Public


If you use Entity Framework 4.0 and you set the Concurrency Mode to Fixed on an object, when you save an object related to that object, the first object will be saved, even though none of its properties have been modified.

I posted a detailed description of this issue, with an example here:

I want to know if the new Entity Framework release in early 2011 will be addressing this serious issue.
Sign in to post a comment.
Posted by Faisal [MSFT] on 1/31/2011 at 3:12 PM

Thanks for sending this issue.

I hope you know that this issue is fixed in a hotfix. Please see details here: http://support.microsoft.com/kb/2390624

Entity Framework Team
Posted by Microsoft on 12/27/2010 at 6:15 PM
Thanks for your feedback. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 12/27/2010 at 1:21 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)