Foreign key constraint issue in WildFly

[valsaraj007]

When we migrated from WidlFly 8, we are getting following error on starting server:

insert or update on table "app_data" violates foreign key constraint "fk1vm6v5waa98rhou9eawcso86m"

However, we are pointing to an existing DB that used on old version and that have a constraint already with name fk4cd3168a78257440.

Then why it is again creating one more with new name? Is there any option to make it use the existing one? 

[simkam]

Hi,

I'm not sure it will help but you could try setting "hibernate.implicit_naming_strategy" to "legacy-hbm".

[valsaraj007]

Thanks for pointing this.

I have applied the following JPA 2.1 annotation to set FK name, so that it will be using same name in both versions of WildFly.

@ManyToOne
@JoinColumn(name = "company_id", nullable = false, foreignKey = @ForeignKey(name="FK_COMPANY__ROUTE"))
private Company company;

https://stackoverflow.com/questions/6608812/jpa-give-a-name-to-a-foreign-key-on-db/21426770