I'm working around this for now by limiting what tables it generates code for to just what I need at the moment.
This is with Postgres. (The server version is 8.4, the jdbc driver is postgresql-9.0-801.jdbc4) There are a good half dozen tables with FK constraints to this table's PK. Actually, looking at one of these tables I see it has TWO identical (except for name) FK constraints to this table. I expect this is a mistake (it's not my schema). Could this be causing it? Actually I can answer my own question. I just tried dropping one of the redundant constraints, recompiled, and sure enough the problem went away. Thanks for the clue to look at dependent FKs! (Note to anyone who runs into this in the future with PostgreSQL: PgAdmin can generate a Dependents Report for a table which made finding this redundant FK very easy.) Eric
