Update 2014-04-29: This is now Possible with Flyway 3.0 by implementing the FlywayCallback interface.
Previous answer
The short answer is: no, not at this point.
Here is the reason: I thought about this as well as I was laying down the initial design for Flyway. The more I thought about this aspect though, the more it became clear to me that these pre and post scripts are also an integral part of the migration, or at least something a migration can not do without if it wants to be successful. Therefore I would recommend to either:
- Merge 1, 2 & 3 in a single migration
- Have 3 separate migrations x.1 (drop views), x.2 (actual migration), x.3 (rebuild views)
You might even be able to have x.1 and x.3 call stored procedures that do the work for you to avoid code duplication between migrations if these steps are repeating.
Having Flyway take care of performing all changes to the database structure makes the whole thing more straightforward, avoiding a mix of different technologies.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…