Hi Manuel,
This idea has been around for a while. In the old days (jOOQ 2.x), there was a third party parser and jOOQ code generator provided by Gudu Software. It only supported parsing MySQL and PostgreSQL dialects, and didn't get a lot of traction from the community, e.g. absolutely no feedback.
At some point, we decided to no longer ship the integration. It can still be found on Github, though:
One reason why the jOOQ parser was introduced in jOOQ 3.9 is precisely this idea, though. We want to re-enact this feature eventually, so you might want to follow this issue here:
It just took the parser a bit of time to mature (still missing a lot of features), and generating Java code instead of SQL code might also raise a few questions, but I think it might be feasible to introduce a first working draft for jOOQ 3.12. Integration testing should work fine as well, we already have tons of parser unit tests. We'll just have to hook the jdk.compiler in between and check for compilation errors.
Do note that you can already parse and translate your DDL from one dialect to another with jOOQ (except you don't get any intermediary Java code). You can play around with this on our website:
Or use the ParserCLI command line tool, or write your own, see:
I hope this helps,
Lukas