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
Migration hierarchy not working #626
Comments
Summarizing the specs to fix this issue here (from Discord): 👉 The proposed solution was to add an index in the migration filename: @josephmancuso is that correct ? |
@yubarajshrestha Are you okay with the specs above ? |
Yes, you're right. You should order those migrations based_on order of migrations added in migrations. .migrations(
"migrations/first_table.py",
"migrations/secon_table.py",
"migrations/third_table.py",
) |
☝️ Yes you're right. But that become a Masonite issue then. I will transfer this issue to the Masonite repo. |
@josephmancuso if you try to migrate the migration with above solution that will give you error if you try migrating. |
Describe the bug
If you have multiple migrations in package development then we need a way to maintain the hierarchy of migrations.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should be able to maintain the order of migrations registered.
The text was updated successfully, but these errors were encountered: