> I'll fix this ASAP Fixing this in jooq-meta and jooq-codegen is easy in jOOQ 3.0, given the few backwards-incompatibilities that are needed to allow for multiple foreign keys per column. However, once this is fixed, new issues arise with other code generation features that expected at most one foreign key per column. These are:
1. Generated setters, setting column values from a referenced record (introduced with #1510) 2. Generated fetch methods While 1) was a feature that I wasn't very happy with from the beginning (various possible and still unresolved naming collision scenarios for little gain of functionality), 2) is a bit more tricky. The fetch methods are probably quite useful to some jOOQ users, but I think I'll have to remove them in the way they are implemented today. Possibly, it would be wiser to add a generic fetch(ForeignKey) and fetchOne(ForeignKey) method, that allows for navigating data through foreign keys... Anyway, given the impact this change seems to have, I doubt I can merge it to a 2.x version. Cheers Lukas
