Describe the bug
When generating migration for updating the table if there's a dropped column with a foreign key constraint, the generated migration first tries to drop the column, which throws an integrity constraint violation exception
Expected behavior
Expected to drop foreign key first, then the column.
Additional context
Isn't it a good idea to use safeUp/safeDown ?
Affected versionsyii2-migration 4.3.0
db MySQL 8.0.28
Describe the bug When generating migration for updating the table if there's a dropped column with a foreign key constraint, the generated migration first tries to drop the column, which throws an integrity constraint violation exception
Expected behavior Expected to drop foreign key first, then the column.
Additional context Isn't it a good idea to use safeUp/safeDown ?
Affected versions
yii2-migration4.3.0dbMySQL 8.0.28