Scenario: ADDRESS(ID, NAME), PERSON (ID, NAME, FK_ADDRESS_ID), CONTACT(ID, NAME, FK_ADDRESS_ID) (See attached changelog.xml)
There are two FK constraints which references the same column in Table ADDRESS.
If you run the migration with dropAll=true, you get an error (see attached File). When he tries to remove the second constraint, you get an error that this constraint doesnt exist anymore. It looks like that he allready removed that constraint. If you execute the migrate with dropAll again, it runs without any error.
Scenario: ADDRESS(ID, NAME), PERSON (ID, NAME, FK_ADDRESS_ID), CONTACT(ID, NAME, FK_ADDRESS_ID)
(See attached changelog.xml)
There are two FK constraints which references the same column in Table ADDRESS.
If you run the migration with dropAll=true, you get an error (see attached File). When he tries to remove the second constraint, you get an error that this constraint doesnt exist anymore. It looks like that he allready removed that constraint. If you execute the migrate with dropAll again, it runs without any error.
With 1.9.2 it is working.