Hibernate可选一对一映射问题：保存客户时抛出标识符生成异常

你遇到的IdentifierGenerationException是因为Customer实体同时对CustomerIndividual和CustomerLegalEntity使用了@MapsId注解。@MapsId的作用是让当前实体的主键值从关联的一对一实体中获取，但当保存个人客户时，customerLegalEntity为null，Hibernate无法确定该从哪个关联实体获取Customer的主键id，因此抛出异常。

方案1：调整映射关系，手动设置Customer主键（贴合现有表结构） #

步骤1：修改Customer实体的映射配置

移除两个@MapsId注解，改用@PrimaryKeyJoinColumn明确主键关联逻辑：

@Data
@Entity
@Table(name = "customer")
public class Customer {

    @Id
    @Column(name = "id_customer", nullable = false)
    private Long id;

    @ManyToOne(fetch = FetchType.EAGER)
    @JoinColumn(name = "fk_customer_type", nullable = false)
    private CustomerType customerType;

    @OneToOne(fetch = FetchType.LAZY, optional = true)
    @PrimaryKeyJoinColumn(name = "id_customer", referencedColumnName = "id_customer_individual")
    private CustomerIndividual customerIndividual;

    @OneToOne(fetch = FetchType.LAZY, optional = true)
    @PrimaryKeyJoinColumn(name = "id_customer", referencedColumnName = "id_customer_legal_entity")
    private CustomerLegalEntity customerLegalEntity;

}

步骤2：完善CustomerLegalEntity的主键生成策略

确保它和CustomerIndividual使用同一个序列生成id，避免主键冲突：

@Data
@Entity
@Table(name = "customer_legal_entity")
public class CustomerLegalEntity {

    @Id
    @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "id_customer_seq")
    @SequenceGenerator(name = "id_customer_seq", sequenceName = "id_customer_seq", allocationSize = 1)
    @Column(name = "id_customer_legal_entity", nullable = false)
    private Long id;

    @NotNull
    @Column(name = "fk_headquarters", nullable = false)
    private Long fkHeadquarters;

    @NotNull
    @Column(name = "name", nullable = false, length = Integer.MAX_VALUE)
    private String name;

}

步骤3：调整保存逻辑

先保存子实体（CustomerIndividual/CustomerLegalEntity），获取其生成的id后，手动设置到Customer实体中：

// 保存个人客户示例
CustomerIndividual individual = new CustomerIndividual();
// 填充individual的业务字段
individual = customerIndividualRepository.save(individual);

Customer customer = new Customer();
customer.setId(individual.getId()); // 手动关联主键
customer.setCustomerType(individualCustomerType); // 设置个人客户类型
customer.setCustomerIndividual(individual);

customerRepository.save(customer);

方案2：改用JPA继承策略（优化架构设计） #

如果允许调整表结构，可以使用JPA的继承映射，将Customer作为抽象父类，CustomerIndividual和CustomerLegalEntity作为子类，更自然地处理不同客户类型的主键关联：

// 抽象父类Customer
@Data
@Entity
@Inheritance(strategy = InheritanceType.JOINED) // 对应现有分表结构
@Table(name = "customer")
public abstract class Customer {

    @Id
    @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "id_customer_seq")
    @SequenceGenerator(name = "id_customer_seq", sequenceName = "id_customer_seq", allocationSize = 1)
    @Column(name = "id_customer", nullable = false)
    private Long id;

    @ManyToOne(fetch = FetchType.EAGER)
    @JoinColumn(name = "fk_customer_type", nullable = false)
    private CustomerType customerType;
}

// 个人客户子类
@Data
@Entity
@Table(name = "customer_individual")
@PrimaryKeyJoinColumn(name = "id_customer_individual", referencedColumnName = "id_customer")
public class CustomerIndividual extends Customer {
    @Column(name = "fk_nationality", nullable = false)
    private Integer fkNationality;
    // ...其他个人客户字段省略
}

// 企业客户子类
@Data
@Entity
@Table(name = "customer_legal_entity")
@PrimaryKeyJoinColumn(name = "id_customer_legal_entity", referencedColumnName = "id_customer")
public class CustomerLegalEntity extends Customer {
    @NotNull
    @Column(name = "fk_headquarters", nullable = false)
    private Long fkHeadquarters;
    // ...其他企业客户字段省略
}

这种方式下，保存客户时直接保存子类实例即可，无需手动处理主键，Hibernate会自动维护父表和子表的关联。

内容的提问来源于stack exchange，提问作者Paul Marcelin Bejan