-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Migrations: Detect primary key property renames #6404
Labels
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
type-enhancement
Comments
I need to think about it more, but my initial feeling is that it becomes even less useful for alternate keys, and indices. |
Also, I wonder if just doing structural matching (e.g. everything is the same except the name) would cover all these cases for much cheaper. |
Triage: we want to have a design discussion about this, including @rowanmiller. |
Closing in favor of doing #6582 instead. |
bricelam
added
the
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
label
Sep 21, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
type-enhancement
Similar to #5155 (but perhaps not as useful), we could also detect renamed properties that are part of the primary key if...
The text was updated successfully, but these errors were encountered: