in domain i have:



With Hibernate 4.3.9 it was creating foreign key with name FK_687us5fhb8bwavfrrwj97o0s7.
After migrating to Hibernate 5.1.5 it creates a duplicate foreign key with name FKdeto0y750974e303dkg4qlh1e.

What i need it to keep the old foreign key name (FK_687us5fhb8bwavfrrwj97o0s7).

I try Hibernate5NamingStrategy without any success, it does not call determineForeignKeyName or determineJoinColumnName methods.

I think it's because of the HHH-11089 which is now fixed in 5.2.9. I don't know if it was backported to 5.1.5, or if it will ever be since Gail decides what needs to be backported.

Try it with 5.2.9, and see if it works, and then add a comment on the issue to mention that it's important for you to have it backported to 5.1.x.

I try with version 5.2.9, but it does not solve my problem.

My problem is the following:
We have more then 100 domains where foreign key name is not defined explicitly. Hibernate generate it automatically.

We need to have hibernate.hbm2ddl.auto=update due to some requirements.

After migrating to Hibernate 5.x, it generate duplicate foreign keys because naming has been changed.

So, now i need somehow to re-implement foreign key naming strategy, in order to use the one used with Hibernate 4.3.9.

I try to re-implement PhysicalNamingStrategy and ImplicitNamingStrategy, but without any success.

How it generate foreign key names?
Shouldn't it call determineForeignKeyName?

Try setting the hibernate.implicit_naming_strategy configuration property to legacy-hbm.