This is now fixed on SVN trunk and will be included in the upcoming version: https://sourceforge.net/apps/trac/jooq/ticket/1270
Identical foreign keys will be ignored, and a warning is issued in source code generation As a matter of fact, Postgres is not the only database allowing for identical foreign keys. Any of these jOOQ databases do: - CUBRID - DB2 - Derby - H2 - Ingres - MySQL - Oracle - Postgres - SQL Server - SQLite - Sybase SQL Anywhere - Sybase ASE This database doesn't allow them: - HSQLDB I have reported a feature request to HSQLDB, to become conformant with the rest: https://sourceforge.net/tracker/?func=detail&aid=3515408&group_id=23316&atid=378134 Cheers Lukas 2012/4/6 ericjs <ericjswry...@gmail.com>: > Yeah a warning sounds like a good idea. I never would have guessed it > was possible either and can't imagine a reason for doing it on > purpose. Maybe the designed wanted to make extra sure that the > constraint could not be violated. ;^)
