Thomas Dudziak schrieb: Hello,
> You should not use the primarykey for this. It would be better if you > add a simple primarykey field to the ProfileMenuCategory, make the > other two fields normal fields, and in the database add a unqiue > constraint on these two fields. This way, the database will throw an > exception when a ProfileMenuCategory object is inserted whose > combination of these fields has already been used. No, this is against everything i know of database design. The way you desribed it you are creating an additional _not_needed_ primary key. An entry in the relation-table is identified by the two foreign keys which together build the primary key of this table. Christoph
pgpAeLk30mAiv.pgp
Description: PGP signature
