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
In current migrations implementation it is possible case when migration fails after implementing some changes.
If such migration fails you must rollback it manually from db.
I know about the problem with transactions for db schema modifications.
But if you have down method with correct commands order php can make these action to revert already applied changes. Iunderstand that it fails when met some not applied changes.
But it will rollback applied changes and you don't need to rollback it manually.
For example it can be implemented as some mode for migrations.
This problem with rollback migrations seems to me very strange as soon as I didn't met it on different Symfony+Doctrine projects with migrations. Doctrine migrations make rollback in any case. Maybe they have some solution for this problem?
The text was updated successfully, but these errors were encountered:
In current migrations implementation it is possible case when migration fails after implementing some changes.
If such migration fails you must rollback it manually from db.
I know about the problem with transactions for db schema modifications.
But if you have down method with correct commands order php can make these action to revert already applied changes. Iunderstand that it fails when met some not applied changes.
But it will rollback applied changes and you don't need to rollback it manually.
For example it can be implemented as some mode for migrations.
This problem with rollback migrations seems to me very strange as soon as I didn't met it on different Symfony+Doctrine projects with migrations. Doctrine migrations make rollback in any case. Maybe they have some solution for this problem?
The text was updated successfully, but these errors were encountered: