You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know there are limitations: if you have changed anything into table between the two migrations, that will be loose. But I think that can be advertised on docs.
The text was updated successfully, but these errors were encountered:
Use case:
Migration A:
xxxxx_create_table_orders.php
Many migrations and months later
Migration Z:
xxxxx_drop_table_orders.php
To make migration Z reversible, I need to implement
up
anddown
methods.The
up
have adrop()
call, so, ondown
I need acreate()
counterpart, with all my schema.Suggestion
If we have one method to call from
down
witch run the migration A::up (or change) would be great. Something like:I know there are limitations: if you have changed anything into table between the two migrations, that will be loose. But I think that can be advertised on docs.
The text was updated successfully, but these errors were encountered: