Dear all,
the strategy for naming foreign keys has changed in hibernate 5.2.x when compared to Hibernate 3.2.6.
I need a way to have a naming strategy that is compatible with the one used in 3.2.6. I've checked the legacy hbm naming strategy, but that strategy produces different naming for foreign keys.
To be clear, I need a naming strategy that produces foreign keys like the following one:

FK8FEF1913C6FD77C9

Does Hibernate 5.2.8 ship such a legacy naming strategy?

Thanks in advance for your help!

A.

Try with the legacy-hbm ImplicitNamingStrategy.

Otherwise, you can also check the migration guides for more info.

As written in the original post



I checked the code:
ImplicitNamingStrategyLegacyHbmImpl extends ImplicitNamingStrategyJpaCompliantImpl but *does not* override the determineForeignKeyName method
which is used afaiu to compute foreign key constraint names and, as such, is backward incompatible.

https://github.com/hibernate/hibernate- ... .java#L200
https://github.com/hibernate/hibernate- ... mImpl.java

You can open a Jira issue and we shall see if the legacy-hbm needs to be changed or a new naming strategy should be provided. I checked in Hibernate 4.3, ana the Foreign Key prefix was "FK_", so this was changed a long time ago.

You should debug it and provide the logic that was used back then. You could also submit a Pull Request, since this is the fastest way to get a fix done.