Entity Framework - Update Stored procedure is triggered for an Unchanged entity when updating a relationship - by Jean Hominal

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 637765 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 1/24/2011 12:14:17 AM
Access Restriction Public


The problem is described in the thread found at that address:

It is a problem where, after having mapped a stored procedure to the update operation of an entity (in the MSL), this stored procedure can be triggered even for entities that are in the "Unchanged" state.

The problem is extremely similar to the one described in that other thread:
Sign in to post a comment.
Posted by Đonny on 11/9/2012 at 9:05 AM
It does not fix the issue for me.
I'm still seeing nonsense UPDATE table SET @p=0.
Using EF 4.3.1 from Nuget.
Posted by BSOD2600 on 6/19/2012 at 1:19 PM
When will this hotfix be included with an official .NET 4 update? I can confirm it fixed my issue with unrelated entities being updated.

Download the hotfix via http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2390624
Posted by Mark Shiffer on 2/2/2012 at 5:47 AM
In exact same situation as the previous two posters. How can I get access to this hotfix without paying?
Posted by rdrenker on 1/31/2012 at 5:54 PM
Better instructions on downloading this hotfix would be very helpful. My attempts to "contact customer support" from that page end up routing me to options where I have to shell out cash.

Could you post a direct link to download this hotfix?
Posted by NYSystemsAnalyst on 8/4/2011 at 11:42 AM
Unfortunately, the KB article does not contain any instructions for downloading this hotfix. All it says is to contact customer support.
Posted by Microsoft on 6/24/2011 at 10:56 AM
This fix is not included in VS 2010 SP1.
Posted by Jon Theriault on 3/25/2011 at 8:35 AM
Can you confirm if this was fixed in VS 2010 SP1?
Posted by Jean Hominal on 1/26/2011 at 1:01 AM
The mentioned hotfix works. Thank you!
Posted by Faisal [MSFT] on 1/25/2011 at 1:18 PM

We have released a hotfix that addresses this issue. Please see http://support.microsoft.com/kb/2390624 for instructions on obtaining the hotfix.

Please let us know if this does not resolve the issue.

Entity Framework Team
Posted by Microsoft on 1/24/2011 at 1:50 AM
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 1/24/2011 at 12:58 AM
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)