| Beginning from 5.2.14 our use case is not working anymore because of the change in  HHH-9460 Closed . Our code looks like in the following:
@Entity
@Table(name = "PARENT")
ParentContainerEntity {
@Id
@Column
private String correlationId;
@OneToMany(orphanRemoval = true, fetch = FetchType.EAGER)
@JoinTable(name = "a_parent_to_a",
joinColumns = {@JoinColumn(name = "correlation_id")},
inverseJoinColumns = {@JoinColumn(name = "a_entity_id")})
private Set<AEntity> aEntities;
@ManyToMany(fetch = FetchType.EAGER)
@JoinTable(name = "a_parent_to_b",
joinColumns = {@JoinColumn(name = "correlation_id")},
inverseJoinColumns = {@JoinColumn(name = "b_entity_id")})
private Set<BEntity> bEntities;
@OneToOne(cascade = CascadeType.ALL, optional = false, orphanRemoval = true)
@PrimaryKeyJoinColumn
private CEntity cEntity;
}
@Entity
@Table(name = "C")
public class CEntity {
@Id
@Column
private String correlationId;
@Lob
@Column(nullable = false)
@Convert(converter = AddressConverter.class)
private List<String> addressLines;
@Column(nullable = false)
private String letterDate;
@Column(nullable = false, length = 500)
private String salutation;
}
Our use case is to share ID of parent without using Bidirectional association and while persisting parent, the child should be persisted with the ID of parent. Before version 5.2.14, order of the relevant insert statements was:
- Hibernate: insert into letter_data (address_lines, letter_date, salutation, correlation_id) values (?, ?, ?, ?)
- Hibernate: insert into std_ex_ante (correlation_id) values (?)
Beginning from version 5.2.14, the order is:
- Hibernate: insert into std_ex_ante (correlation_id) values (?)
- Hibernate: insert into letter_data (address_lines, letter_date, salutation, correlation_id) values (?, ?, ?, ?)
This happens because parent has a foreign key constraint onto ID of child. If the parent will be persisted as first, child and ID of it does not exist, which causes ConstraintViolationException on flush. Problem in code is in class OneToOneSecondPass.java
if ( value.isReferenceToPrimaryKey() ) {
value.setForeignKeyType( ForeignKeyDirection.TO_PARENT );
}
else {
value.setForeignKeyType(
value.isConstrained()
? ForeignKeyDirection.FROM_PARENT
: ForeignKeyDirection.TO_PARENT
);
}
Beginning from version 5.2.14 value.setForeignKeyType will be set to ForeignKeyDirection.TO_PARENT in our code. It was and should be set to ForeignKeyDirection.FROM_PARENT before version 5.2.14. I tested this with the code above on 5.2.13.Final and there is no problem. |
