Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Model Builder: Generating non-unique FK constraint names #6815

Closed
HappyNomad opened this issue Oct 19, 2016 · 4 comments
Closed

Model Builder: Generating non-unique FK constraint names #6815

HappyNomad opened this issue Oct 19, 2016 · 4 comments
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone

Comments

@HappyNomad
Copy link

I discovered this issue while looking for a workaround to #6814. It can be reproduced using the context and model posted there, with this modification of swapping the names of A's M1 and M2 properties. This produces an SqlException with the text, "Cannot create, drop, enable, or disable more than one constraint, column, index, or trigger named 'FK_PBase_MT_MTID' in this context. Duplicate names are not allowed."

@rowanmiller
Copy link
Contributor

We think this is fixed in 1.1. Could you retry it on Preview 1 and see if it is resolved?

@rowanmiller
Copy link
Contributor

@HappyNomad
Copy link
Author

Okay, I tried and this bug appears to be resolved.

@rowanmiller
Copy link
Contributor

Thanks!

@rowanmiller rowanmiller changed the title Generate unique FK constraint names Model Builder: Generating non-unique FK constraint names Oct 26, 2016
@rowanmiller rowanmiller added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 26, 2016
@rowanmiller rowanmiller added this to the 1.1.0-preview1 milestone Oct 26, 2016
@ajcvickers ajcvickers modified the milestones: 1.1.0-preview1, 1.1.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Development

No branches or pull requests

4 participants