[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-682?page=co... ] Emmanuel Bernard commented on ANN-682: -------------------------------------- IM chat: don't know if you want/can do anything about this: @ForeignKey in a @MappedSuperclass is inherited in subclasses so these all get the same FK name in the catalog which doesn't work so right now i don't see a way to have a @ManyToOne in a @MappedSuperclass and then customize the foreign key constraint emmanuel 09:32 I see. Yes open a JIRA issue. I'm not sure how to solve that cleanly though christian 09:32 maybe a hibernate specific @AttributeOverride emmanuel 09:33 yes that could do it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-682?page=co... ] Eugene Voytitsky commented on ANN-682: -------------------------------------- Did I understand right that currently Hibernate doesn't have possibility to rename name of auto-generated foreign key constraint for association which is defined in my @MappedSuperclass? In other words, if I have @ManyToOne association in my @MappedSuperclass class and number of entity subclasses then I have no way to explicitly specify (rename) the names of foreign keys in each entity subclass: neither @AttributeOverride nor @AssociationOverride provides the possibility to specify foreign key name. It's a pity. Actually I only have very ugly solution/workaround: because I use @AccessType("filed") strategy for my @MappedSuperclass class I can change the strategy to @AccessType("property") on all entity subclasses and fully redefine the association on getter method, something like this: @AccessType("property") public class Entity1 extends MyBaseClass { @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "user_id", nullable = false) @ForeignKey(name = "fk_entity1_2_user") public User getUser() { return super.getUser(); } Everything smells bad in this "solution": * changing the strategy * full redifinition of the association * and even invocation of super.getUser() Is it going to be improved in the upcoming Hibernate releases? Thanks in advance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-682?page=co... ] Jean-Christian Gagné commented on ANN-682: ------------------------------------------ Using a custom NamingStrategy could be an easy (but not protable) workaround. But the current API doesn't let me customize constraint names (primary, foreign, ...). Or does it ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4329?page=c... ] David D commented on HHH-4329: ------------------------------ My "workaround", which is more a best practice in my opinion : generate the schema with hbm2ddl and change any fk name you like (or any constraint name for the matter). Then use this file to create your database. But that's maybe not what you want to hear... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira