Model Builder: Generating non-unique FK constraint names #6815
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
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."The text was updated successfully, but these errors were encountered: