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

Difference migration feature request #94

Open
mehmetdemiray opened this issue Oct 6, 2022 · 1 comment
Open

Difference migration feature request #94

mehmetdemiray opened this issue Oct 6, 2022 · 1 comment

Comments

@mehmetdemiray
Copy link

mehmetdemiray commented Oct 6, 2022

App is migrating everything as combined currently. My feature request is separated migrations. For example I created new scheme and it created migrations it's ok. After that if i add new field in model it needs to create new migration.

Maybe one more button needs like "Save Migration". If you click save button migrations appear combined. If you click migrate button it create new migration according to the difference with the last changes. Because as you know after start the project we can not changes migrations only we can add new ones for changes.

@tomjschuster
Copy link
Owner

I agree that currently the generated migrations are only useful for new projects/tables; this request makes sense.

I like the "Save Migration" idea and would love to dig into this when I have some time.

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

No branches or pull requests

2 participants