Is determinePrimaryKeyJoinColumnName() ever used in Hibernate 5 ImplicitNamingStrategy?
Description
Activity
Show:
Christian Beikov April 8, 2022 at 12:31 PM
Since no test case was provided for years, I'll close this issue as out of date. I also believe it will most probably not be an issue any more in 6.0.
If this still is an issue for you, please create a new issue with a test case that reproduces the problem.
Thomas Anderegg January 20, 2017 at 5:22 PMEdited
I run into the same problem with
@DiscriminatorColumn@MapKeyColumn@OrderColumn
where my ImplicitNamingStrategy is never called.
Benjamin Ellenberger August 16, 2016 at 10:43 AM
I probed this already on stackoverflow and it seems to be confirmed that this issue exists by several users:
http://stackoverflow.com/questions/38263233/is-determineprimarykeyjoincolumnname-ever-used-in-hibernate-5-implicitnamingst
Out of Date
Details
Details
Assignee
Unassigned
UnassignedReporter
Benjamin EllenbergerLabels
Original estimate
Time tracking
No time logged1h remaining
Components
Affects versions
Priority
MinorCreated August 16, 2016 at 10:42 AM
Updated April 8, 2022 at 12:31 PM
Resolved April 8, 2022 at 12:31 PM
I am working on hibernate 5 and implemented the ImplicitNamingStrategy interface. Among other methods, there are two methods called determinePrimaryKeyJoinColumnName(...) and determineJoinColumnName(...). In the java doc, it says about determinePrimaryKeyJoinColumnName:
I annotated my joins with PrimaryKeyJoinColumn and the code works, however the names never get routed through determinePrimaryKeyJoinColumnName(...) but through determineJoinColumnName(...).
Am I wrong in believing this is a bug?