-
-
Notifications
You must be signed in to change notification settings - Fork 525
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
Shouldn't db:migrate detect old_schema and convert table automatically? #82
Comments
That would probably make sense. Are you in the mood to provide a PR ? |
Yup, of course! How would you prefer? I have 3 proposals:
|
Do you have an opinion about a special entry in the config file? |
Nice! That makes more sense! What name do you prefer: |
Probably the latter one as it states |
I prefer the last one also. Doing it. |
Great thanks! |
fix small typo in spec
Since we and many more of us have auto-deploy on green,
sequelize db:migrate:old_schema
command doesn't seems to be a nice approach. Specially for those (our case) who have servers running and protected against manual access.Shouldn't
db:migrate
task check if it needs to migrate fromold_schema
and migrate automatically?ping @sdepold @mickhansen
The text was updated successfully, but these errors were encountered: