Hibernate Team |
|
Joined: Tue Aug 26, 2003 7:19 pm Posts: 2364 Location: Brisbane, Australia
|
When it finds there is no primary key(s) defined it will generate a single large composite key since it has the best chance of being unique. The Relational model your using is not correct (which I sure you already know). It is too difficult (where the reality is i'm not motivated) to allow custom selection of fields that can pretend to be the primary key. I suggest you hand edit the table HBMs in question or better still add the primary constraints to the legacy database. Maybe you would be allowed to just change the development database to help.
|
|