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
Migration history table stores only version and apply_time.
But there's a problem when we need to migrate down - we need to specify exact migrationPath for migrations we want to revert!
The text was updated successfully, but these errors were encountered:
The current implementation assumes that migrations are all located in one place. this will be solved when we support multiple paths. duplicate of #384.
Just for others who will meet the same problem.
I've used different migrationPath for installing CMS extensions migrations.
I have information on migrationPath and extension ID.
Therefore solution was to separate all extensions migrations to separate table - one table for one migration.
The better solution is expected from solving #384
Migration history table stores only version and apply_time.
But there's a problem when we need to migrate down - we need to specify exact migrationPath for migrations we want to revert!
The text was updated successfully, but these errors were encountered: