Hi: This is not a JOOQ feature/issue related question, but more of a best practice question.
We are using JOOQ + Flyway in our Dev landscape, however we are doing manual DB patches in our Staging and Production DBs. The issue is that whenever we do DB changes and do a Test / Build it works (as a new DB instance is spun up for building and testing and the Flyway migrations are done), however when we deploy to Staging there are times where the DB patching is not done and the generated classes are out of sync with the DB. Wanted to check if anyone has any similar set-ups and would like to get some opinions/practices on how to prevent deployment to Staging / Prod if the DB patching is not done. -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/d5400c68-d9a5-46a6-9d07-18663afd6fdcn%40googlegroups.com.
