6

My question is, has anyone found a satisfactory formula for migration large and frequently changing stored procedures?

This question touches on it and has a response from the Flyway author but it's been over a year and a major release with exciting new framework hooks has since been published.

I've added a more thorough description of the problem and my current solution to this flyway github issue but I thought I'd reach out to a wider audience. As described, I have a working solution but has inelegant aspects to it.

I'm wondering if MigrationResolvers or FlywayCallbacks can be put to good use here?

Community
  • 1
  • 1
markdsievers
  • 7,151
  • 11
  • 51
  • 83
  • have queried similar in https://github.com/flyway/flyway/issues/1107 and http://forum.liquibase.org/#Topic/49382000001383021 – Straff Oct 15 '15 at 02:06
  • Liquibase has a pretty good solution for this: the changeSet only includes an external script file and is marked as "run on change". So each time the included file has changed (based on the MD5 hash) Liquibase will run it - this requires that the file can always be run successfully (so it's only usable with "create or replace" types of scripts) - maybe Flyway has something similar? –  Oct 16 '15 at 07:02

1 Answers1

3

Repeatable Migrations!

Purpose built for this situation, did not exist at time of asking in the 3.x release.

markdsievers
  • 7,151
  • 11
  • 51
  • 83