> The best way to thoroughly solve this is probably to put foreign key > declarations in table classes, directly. I'll fix this as issue #1459: > https://sourceforge.net/apps/trac/jooq/ticket/1459
Unfortunately, this is not going to work easily. The Keys.java class simplifies static initialisation of jOOQ-generated artefacts. It is always the last artefact to be loaded by the ClassLoader (when all tables / records, etc. have already been loaded). Also, unique keys are loaded before foreign keys (which reference them). Changing that will open pandora's box on static initialisation. I'll have to think about some other solution... Cheers Lukas
