Schematisations may already contain any of the table names that are in the new schematisation. To prevent conflicts, I added a step to drop those at the beginning of each migration.
I did not make a separate hotfix for 225 because it is unlikely that the 225 package will be run in the wild, and I don't see this as a bug bug more as a user error ;).
Schematisations may already contain any of the table names that are in the new schematisation. To prevent conflicts, I added a step to drop those at the beginning of each migration.
I did not make a separate hotfix for 225 because it is unlikely that the 225 package will be run in the wild, and I don't see this as a bug bug more as a user error ;).