A collection with cascade=“all-delete-orphan“ was no longer referenced by the owning entity instance

天-堂

已于 2022-09-07 11:24:39 修改

阅读量4.3k

点赞数 1

分类专栏： Java 文章标签： hibernate java 后端

于 2022-08-09 11:45:19 首次发布

本文链接：https://blog.csdn.net/qq_41800663/article/details/126244410

版权

Java 专栏收录该内容

2 篇文章

订阅专栏

本文介绍了一种常见的JPA更新数据库时出现的异常——“Acollectionwithcascade=all-delete-orphanwasnolongerreferencedbytheowningentityinstance”，并提供了正确的更新集合属性的方法。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance: com.ifreecomm.education.business.domain.model.questionIdentify.TaskIdentifyPage.partInfos; nested exception is org.hibernate.HibernateException: A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance: com.ifreecomm.education.business.domain.model.questionIdentify.TaskIdentifyPage.partInfos

JPA 更新数据库异常：A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance。

该异常是因为级联更新关联表数据时操作错误导致的

 @Setter
 @OneToMany(orphanRemoval = true, cascade = CascadeType.ALL, fetch = FetchType.EAGER)
 @JoinColumn(name = "identifyPageId")
 private Set<TaskIdentifyPartInfo> partInfos = new HashSet<>();

更新该字段时不能使用setPartInfos()，需要使用set类的add或者addAll方法进行更新。

正确操作为：

public void updatePartInfos(Set<TaskIdentifyPartInfo> partInfos) {
    if (CollectionUtils.isEmpty(partInfos)) {
        return;
    }
    this.partInfos.clear();
    this.partInfos.addAll(partInfos);
}