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

Migrations become destructive when renaming multiple enums #84

Open
tmrkus opened this issue Oct 19, 2017 · 1 comment
Open

Migrations become destructive when renaming multiple enums #84

tmrkus opened this issue Oct 19, 2017 · 1 comment

Comments

@tmrkus
Copy link

tmrkus commented Oct 19, 2017

If you rename enum A -> A' and then B -> A, database migrations become destructive. Both enums and columns using it are dropped and then recreated .

When you just rename A -> A', run the migrations, and then rename B -> A, everything works as expected.

@zapov
Copy link
Member

zapov commented Nov 19, 2017

This is unlikely to change until some specialized migration language is introduced. It doesn't seems like a big problem to have refactoring done in multiple steps :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants