We have a jdbc.initScript property, which can be used to initialise a database prior to code generation:
https://www.jooq.org/doc/latest/manual/code-generation/codegen-system-properties/

This is very useful for quick tests, including MCVEs:

• Use jdbc/initScript property instead of sql-maven-plugin jOOQ-mcve#46

The feature has been introduced with 3.16:

• Additional SQL statements after JDBC connection #12759

Unfortunately, it can only run inline scripts, not scripts from the file system. Let's support reading scripts from the file system as well.

• If the script describes a classpath resource, load that resource
• If the script describes a file that exists, load that file
• If the script describes a directory that exists, load all files from that directory, ordered alphabetically (out of scope for now)
• Otherwise, try to execute the content, as before