Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

HBM mapping incorrectly handles reference by non primary key

Description

Assume having the following entities:

class EntityA { int id; int referenceKey; Set<EntityB> bs; } class EntityB { int id; // join column referencing the `EntityA(referenceKey)` instead of `EntityA(id)` EntityA a; }

Mapping these with annotations works just fine. Mapping it with HBM:

<many-to-one name="a" property-ref="referenceKey" not-null="true"> <column name="smth" /> </many-to-one>

leads to:

Referential integrity constraint violation: "FKKM37PO9RU1CDO9KUIP6C7I0UG: PUBLIC.T_CHILD FOREIGN KEY(PARENTVAL) REFERENCES PUBLIC.T_PARENT(ID) (CAST(99999 AS BIGINT))"; SQL statement: insert into T_CHILD (name,parentVal,id) values (?,?,?) [23506-232] org.h2.jdbc.JdbcSQLIntegrityConstraintViolationException: Referential integrity constraint violation: "FKKM37PO9RU1CDO9KUIP6C7I0UG: PUBLIC.T_CHILD FOREIGN KEY(PARENTVAL) REFERENCES PUBLIC.T_PARENT(ID) (CAST(99999 AS BIGINT))"; SQL statement: insert into T_CHILD (name,parentVal,id) values (?,?,?) [23506-232]

 

(see https://hibernate.atlassian.net/browse/HHH-19183 (97286943868bbadb43e892e517a07bf232702058))

Activity

Show:

Marko BekhtaFebruary 26, 2025 at 5:19 PM

Turned out we don't actually need to remove the fix. closing the issue.

Won't Fix

Details

Assignee

Reporter

Worked in

Affects versions

Priority

Created February 24, 2025 at 9:40 AM
Updated February 26, 2025 at 5:19 PM
Resolved February 26, 2025 at 5:19 PM

Flag notifications