This forum topic is about the same problem: http://galaxy.andromda.org/forum/viewtopic.php?t=4733

Hi,

Now I am confused after reading this other thread. I see two issues here which need to be resolved:

1) Users need a mechanism to control foreign key *column* names
2) Users need a mechanism to control foreign key *constraint* names

We have two namespace properties and a tagged value:

foreignKeySuffix
constraintSuffix
@andromda.persistence.foreignkey.constraint


From my use of the EJB3 cartridge *none* of the above 3 tools affect the foreign key constraint name. They only affect the foreign key column name. Is something broken or not implemented right?

-Leandro

I'm thinking we should use @andromda.persistence.column to explicitly define the foreign key column name and @andromda.persistence.foreignkey.constraint to explicityly define the foreign key constraint name. I've made a few changes locally and will need to test further before committing.

Also, I think it makes more sense to have _FK as the suffix for the FK column name instead.

Fix now in cvs. Pls read the cartridge relationship howto for further info.