Regarding 4) among the pros, jOOQ does this (opt in): https://www.jooq.org/doc/dev/manual/sql-building/queryparts/sql-transformation/transform-patterns https://

Regarding 4) among the pros, jOOQ does this (opt in): https://www.jooq.org/doc/dev/manual/sql-building/queryparts/sql-transformation/transform-patterns https://www.jooq.org/doc/dev/manual/sql-building/queryparts/.... It's being done at runtime, thus probably not to be done in production, but during your integration tests as part of the diagnostics feature set: https://www.jooq.org/doc/dev/manual/sql-building/dsl-context/custom-settings/settings-diagnostics-logging/ https://www.jooq.org/doc/dev/manual/sql-building/dsl-context... Regarding 2) among the cons: The recommended approach is to use testcontainers: https://blog.jooq.org/using-testcontainers-to-generate-jooq-code/ https://blog.jooq.org/using-testcontainers-to-generate-jooq-... Reverse engineering a SQL script is also possible, though limiting in terms of what syntax is available in DDL: https://www.jooq.org/doc/dev/manual/code-generation/codegen-ddl/ https://www.jooq.org/doc/dev/manual/code-generation/codegen-... If your cons are too much to handle, then you can still revert to using native SQL and profit from 1) and 4) by using jOOQ's parser: https://www.jooq.org/doc/dev/manual/sql-execution/parsing-connection/ https://www.jooq.org/doc/dev/manual/sql-execution/parsing-co... Escape hatches are simple, too: https://www.jooq.org/doc/dev/manual/sql-building/plain-sql-templating/ https://www.jooq.org/doc/dev/manual/sql-building/plain-sql-t...