Hello,

I am playing a bit with FluentMigrator. I use runner.MigrateUp() to apply modification in my db as explained in the documentation. When the migration code is correct everything works as expected but then I put an error in my SQL, for exemple a wrong column name in a ForeignKey constraint, The Exception is thrown and the migration is simply stopped. I expected a rollback of the current migration (class) at least but apparently not.
Is that expected? How should I write the migration so all the change MigrationUp has down is rolled back like in a transaction?

Thanks.
Best regards.

EDIT 1 :
I think I have undestood a part of the problem. In MariaDB (I use MySql5 as it is a fork), DDL statements create new transaction every statement so this cannot work.
But the question remain. How should I handle the case properly?