EF5 migrations: foreign key violation while modifying primary key - by spongman

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<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 780142 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/27/2013 12:03:48 PM
Access Restriction Public


ef5 generates invalid migrations when modifying a primary key when that primary key appears in a foreign key relationship.

it needs to drop/re-create the foreign keys whenever performing such transformations.
Sign in to post a comment.
Posted by Rowan Miller on 3/7/2013 at 2:27 PM
Hello, Thank you for reporting this issue, we have moved it to our public back log where you can view its status and vote on it - http://entityframework.codeplex.com/workitem/937.
If you encounter any further issues please report them via the Entity Framework CodePlex site - http://entityframework.codeplex.com/WorkItem/Create. ~Rowan
Posted by Microsoft on 3/6/2013 at 12:17 AM
Thanks for your feedback.

We are rerouting 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 3/4/2013 at 3:20 AM

Sorry for bothering. Is there any update?

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thank you!
Posted by Microsoft on 2/27/2013 at 10:06 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please use the feedback tool to collect steps while you're repro'ing the issue?

Visual Studio now has an extension called Microsoft Visual Studio 2012 Feedback Tool, available on the VS gallery(http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c4cfe72).

The extension allows you to
1. upload files,
2. collect trace and dump files
3. collect steps while you're repro'ing the issue, as well as
4. SQM logs about VS extensions installed
5. System details (in DxDiag output)

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 2/27/2013 at 12:50 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)