Clean on DB2 does not clean triggers. #802
seems to be related to #462. However, this does not only happen in Oracle Comp mode.
Using Flyway 3.0 btw.
In our case we move a table to another tablespace (using sysproc.admin_move_table) and in a later migration create an alter trigger on a table that is dependent on the moved one. This trigger inserts values in a table created in a later migration (between move and trigger creation).
First try, everything works fine.
Actually, I think this could also be considered a bug in DB2 because one would assume that droping a table should also drop all triggers on that table.
Thank you very much for the issue and the pull request. I don't know why my initial tests failed to reproduce this.
Merged and will be part of Flyway 3.1 due out later this month.
I've also added you to the hall of fame page. (flyway 3.1 branch until merged)