In https://sourceforge.net/apps/trac/jooq/ticket/1510, you write:
> It avoids naming clashes, if a table X has two single-column foreign keys to another table Y > The latter is important, specifically if X has only one reference to Y at first, but then another reference gets added later. If the method name would be changed, then client code would break. I can't follow you here. If I add a second FK reference to X, I'll have to give this column (or columns) a new name, so there can't be a name clash (there are no back-references from Y to X generated by this). Am I missing something? Regards, A. Digulla
