> From a quick glance at the code, I think that jOOQ's core model of > referential meta data (org.jooq.UniqueKey, org.jooq.ForeignKey) will > not be affected, so this is a jOOQ-meta (and thus, jOOQ-codegen) issue > only. It shouldn't be too hard to fix.
I can easily reproduce this issue with the H2 database. and the following test table: CREATE TABLE x_test_case_2025 ( ref_id int NOT NULL, ref_name VARCHAR(10) NOT NULL, CONSTRAINT fk_x_test_case_2025_1 FOREIGN KEY(ref_id) REFERENCES x_test_case_85(id), CONSTRAINT fk_x_test_case_2025_2 FOREIGN KEY(ref_id) REFERENCES x_test_case_71(id), CONSTRAINT fk_x_test_case_2025_3 FOREIGN KEY(ref_id, ref_name) REFERENCES x_unused(id, name) ); I'll fix this ASAP Cheers Lukas
