Have been using this in production for some years now. It works great. The tool itself is highly opinionated though, it has been tuned to DB schema's that use the features I like. YMMV.

The jOOQ code generator is missing various features that prevents its use in a fully automated way. The standard workaround is to maintain two lists of SQL scripts; one for the DB to do the migration and one for the code generator to work on.

Alternatively you can try rewriting your migration scripts to be parsable by both. However there are some features that are really hard to get around because of limitations in the parser.

This preprocessor seeks to make development easier by taking the migration scripts and converting them to what the parser can handle. The parser can then operate on the reduced set of instructions.

• Cannot handle semicolons in column comments