I wanted to give meaningful names to my foreign keys & constraints.

Quite easy, I thought... Just add @ForeignKey on all the @ManyToOne properties that generate the foreign keys, and that's it...

But - This becomes a problem for properties inside reusable @Embeddable classes (e.g. Address)...

When several tables embed the Address component, the @ForeignKey attempts to create the same constraint name in all these tables.

This causes MYSQL to become very angry, because it requires uniqueness among all constraint names in a database.

How can I force a meaningful constraint name on fields of embeddable objects? I couldn't find a way to override the @ForeignKey definition at the 'instantiation' (@Embedded) location...

Any help would be appreciated.

Thanks,
Michael

I am also looking for the same thing but for a different reason. I have @MappedSuperclass's and @Inheritance classes w/ foreign keys that I need custom names for to keep my dba happy.

Since the annotation will always have problems w/ dynamic generation, I think updating the NamingStrategy iface (mentioned in this post) would be the best solution.

I attempted a custom dialect extension but the getAddPrimaryKeyConstraintString only contains one of the two table names I need to generate a friendly FK name.

Would a patch to NamingStrategy (w/ impl's in Default and Improved) be accepted?