Spring Boot已有客户销售单保存失败报detached entity错误，新客户正常

问题描述 #

在Spring Boot项目中，SalesOrder与Customer为一对一关联，新增客户时销售单可正常保存，但使用已有客户保存销售单时失败，抛出异常：

detached entity passed to persist: com.jee.cms.app.customer.model.Customer; nested exception is org.hibernate.PersistentObjectException: detached entity passed to persist: com.jee.cms.app.customer.model.Customer

实体类代码 #

SalesOrder.java

@Entity
@Table(name = "sales_order")
@EntityListeners(AuditingEntityListener.class)
public class SalesOrder extends Auditable<String>  implements Serializable {
    
    private static final long serialVersionUID = 1L;
    
    @Id
    @GeneratedValue(strategy= GenerationType.IDENTITY)
    private Long id;
    
    @OneToOne(fetch = FetchType.EAGER,cascade=CascadeType.ALL)
    @JoinColumn(name = "customer_id", nullable = false)
    private Customer customer;
}

Customer.java

@Entity
@Table(name = "customer")
@EntityListeners(AuditingEntityListener.class)
public class Customer extends Auditable<String>  implements Serializable {
    
    private static final long serialVersionUID = 1L;
    
    @Id
    @GeneratedValue(strategy= GenerationType.IDENTITY)
    private Long id;
    
    @OneToOne(mappedBy="customer",cascade={CascadeType.DETACH, CascadeType.MERGE, CascadeType.PERSIST,CascadeType.REFRESH})
    private SalesOrder salesOrder;
}

业务处理代码 #

SalesOrder salesOrder = new SalesOrder();
Branch branch = BranchContextHolder.getCurrentBranch();
String nextSequense = null;
if(salesOrderDto.getId()==null) {
    salesOrder = new SalesOrder(salesOrderDto);
    salesOrder.setBranch(branch);
    if(customerRepository.existsByPhone(salesOrderDto.getCustomer().getPhone())) {
        Customer customer = customerRepository.findCustomerByPhone(salesOrderDto.getCustomer().getPhone());
        customer.setSalesOrder(salesOrder);
        salesOrder.setCustomer(customer);
    }
    nextSequense = sequenceService.getNextSequense(branch.getId(),module.getId());
    salesOrder.setUid(nextSequense);
}

//save sales order
salesOrder = salesOrderRepository.save(salesOrder);

原因分析 #

1. 级联策略冲突：SalesOrder的@OneToOne注解配置了cascade=CascadeType.ALL，意味着保存SalesOrder时，Hibernate会对关联的Customer执行所有级联操作，包括persist。
2. 分离实体触发异常：通过customerRepository.findCustomerByPhone查询到的已有Customer属于分离状态（查询结束后Session关闭，实体脱离了Hibernate的持久化上下文）。此时将该分离实体关联到SalesOrder并执行save操作时，Hibernate会尝试对其执行persist，但persist仅支持瞬时状态（无主键ID）的实体，已有客户的ID已存在，因此触发detached entity passed to persist异常。

解决方案 #

方案1：调整SalesOrder的级联类型 #

将SalesOrder中@OneToOne的级联策略从CascadeType.ALL改为仅包含必要操作的组合，比如MERGE和REFRESH，避免对已有客户执行不必要的persist操作：

@OneToOne(fetch = FetchType.EAGER, cascade={CascadeType.MERGE, CascadeType.REFRESH})
@JoinColumn(name = "customer_id", nullable = false)
private Customer customer;

这种方式最直接，因为已有客户不需要重新持久化，只需要合并关联关系即可。

方案2：手动合并分离实体到持久化上下文 #

在将Customer关联到SalesOrder之前，通过EntityManager.merge()将分离状态的Customer转换为持久化状态：

// 需注入EntityManager
@Autowired
private EntityManager entityManager;

// 业务逻辑中修改
if(customerRepository.existsByPhone(salesOrderDto.getCustomer().getPhone())) {
    Customer customer = customerRepository.findCustomerByPhone(salesOrderDto.getCustomer().getPhone());
    // 合并实体，使其回到持久化上下文
    customer = entityManager.merge(customer);
    customer.setSalesOrder(salesOrder);
    salesOrder.setCustomer(customer);
}

merge方法会将分离实体的状态同步到持久化上下文中的实体，后续保存SalesOrder时，Hibernate会正确处理关联关系。

方案3：分情况处理级联逻辑 #

如果需要保留新增客户时的级联保存功能，可在业务代码中区分客户是否为新实体（通过ID是否为null判断），动态处理：

if(customerRepository.existsByPhone(salesOrderDto.getCustomer().getPhone())) {
    Customer customer = customerRepository.findCustomerByPhone(salesOrderDto.getCustomer().getPhone());
    salesOrder.setCustomer(customer);
    // 已有客户，手动维护反向关联，不依赖级联persist
    customer.setSalesOrder(salesOrder);
    customerRepository.save(customer);
} else {
    // 新客户，使用原有级联策略
    Customer customer = salesOrderDto.getCustomer();
    customer.setSalesOrder(salesOrder);
    salesOrder.setCustomer(customer);
}

这种方式需要分别处理新老客户的保存逻辑，适合业务场景复杂的情况。

内容的提问来源于stack exchange，提问作者Jeebendu kumar Behera