JOOQ purely depends upon the code generated from SQL schema. Any sane guy who is interested in JOOQ would usually love a tight control on database schema out of which JOOQ artifacts are generated.
JOOQ should come with a database schema version tool. http://migrate4j.sourceforge.net/ seems simple and promising but current state is dormant in terms of DB support. https://github.com/azomazo/migrate4j has more databases supported and seems workable. This would overcome following disadvantage of JOOQ, "When you need to write DDL statements. jOOQ only supports DML statements." workflow becomes . 1. define your schema using migrate4j or something similar 2. apply it using "ant task" or "maven task" 3. And then regular JOOQ workflow.. Advantages, Everything gets source controlled in a repository using pure Java.
