{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 别忘想泡老子 的问题《Flyway: Strategy for migrating frequently changing》','https://www.manongdao.com/q-583823.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
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?
Repeatable Migrations!
Purpose built for this situation, did not exist at time of asking in the 3.x release.