Flyway: a strategy for porting frequently changing functions / stored procedures

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

This question affects him and has an answer from the author of Flyway, but more than a year has passed, and since then a major issue has been published with exciting new frameworks.

I have added a more detailed description of the problem and my current solution is the issue of a trip , but I thought I would reach a wider audience. As described, I have a working solution, but it has inelegant aspects.

I am wondering if it is possible to use MigrationResolvers or FlywayCallbacks here?

+3
source share
1 answer

Recurring migrations

The purpose built for this situation did not exist at the time of the request in release 3.x.

+1
source

All Articles