@JoinColumnsOrFormulas: referencedColumnName throws MappingException "Unable to find column with logical name: ..."
Description
Activity
Christian Beikov January 15, 2025 at 1:38 PM
The Hibernate ORM test suite has a bunch of tests that exercise the mapping that you posted here, so I'll assume this was fixed at some point.
Steve Ebersole October 28, 2015 at 3:26 AM
As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.
Steve Ebersole October 27, 2015 at 7:15 PM
This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.
For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/
The following AnnotationMapping throws a MappingException ...
Unable to find column with logical name: id in org.hibernate.mapping.Table(template) and its related supertables and secondary tables
This is caused by identifying the column names within the logicalToPhysical map of TableColumnNameBinding. Within this map the column names are surrounded by grave accents (`id`) while the check do a lookup to the map with plain column name (id).
A workaround for this issue is surrounding the column name with gave accents.