我正在尝试在Hibernate 4.3.5 / JPA2对象中使用orphanRemoval,但它似乎没有像我预期的那样工作。但是,如果我做错了什么,或者这仍然是Hibernate中的错误,我不确定。
考虑到以下关系(为了简洁省略了@Version,getters和setter):
@Entity
public class Provider implements Serializable {
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
@Column(name = "id")
private Long id;
private String name;
@OneToMany(orphanRemoval=true,cascade=CascadeType.REMOVE)
@JoinColumn(name="provider_id", referencedColumnName="id")
private List<Contract> contracts;
}
@Entity
public class Contract implements Serializable {
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
@Column(name = "id")
private Long id;
private String volume;
@OneToMany(orphanRemoval=true,cascade=CascadeType.REMOVE) // delete any attachments that were previously uploaded with this contract
@JoinTable(name="contract_attachment", joinColumns = @JoinColumn(name = "contract_id", referencedColumnName = "id"), inverseJoinColumns = @JoinColumn(name = "attachment_id", referencedColumnName = "id"))
private List<Attachment> attachments;
}
@Entity
public class Attachment implements Serializable {
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
@Column(name = "id")
private Long id;
private String filename;
}
如果我从Provider.contracts列表中删除合同,我希望它会从合约表中删除相应的行,并从附件表中删除所有相关的附件。但是,只有合同表被删除。附件表未被修改。
例如:
// loop over all contracts and delete the one with the matching id
for(Iterator<Contract> it = provider.getContracts().iterator(); it.hasNext();){
Contract c = it.next();
if( c.getId() == contractId ){
it.remove();
break;
}
}
鉴于附件是相对于合同表的ManyToOne,如果删除合同,则附件是孤立的。但即使使用orphanRemoval=true
,也不会删除数据库中的行。
我在Hibernate 3中找到了几个与此相关的问题(这里都是SO,Jira和其他地方的在线),但我已经明白它已在Hibernate 4中修复了。但是使用Hibernate 4.3.5我仍然看到这个问题。从this issue开始,它似乎有效,所以我不确定为什么我无法使其正常运行。
我的代码中是否存在错误/缺失,或者Hibernate是否仍存在问题?我是否需要在equals
的任何实体类中实施hashCode
和orphanRemoval
才能正常运行?我尝试在合同和附件中实现这两种方法,但没有任何区别。
查看Hibernate日志,它显示Hibernate对连接表(或FK映射)进行了更改,但实际上并未从关联表中删除该行。我可以在Contract表中看到Hibernate设置provider_id = null,但不应该删除Contract行吗?
2014-07-04 15:06:41,333 [main] [-] DEBUG org.hibernate.SQL -
/* update
com.ia.domain.Provider */ update
provider
set
default_contact_id=?,
name=?,
type=?,
version=?,
website=?
where
id=?
and version=?
Hibernate:
/* update
com.ia.domain.Provider */ update
provider
set
default_contact_id=?,
name=?,
type=?,
version=?,
website=?
where
id=?
and version=?
2014-07-04 15:06:41,334 [main] [-] TRACE hibernate.type.descriptor.sql.BasicBinder - binding parameter [1] as [BIGINT] - [null]
2014-07-04 15:06:41,334 [main] [-] TRACE hibernate.type.descriptor.sql.BasicBinder - binding parameter [2] as [VARCHAR] - [name_3]
2014-07-04 15:06:41,335 [main] [-] TRACE org.hibernate.type.EnumType - Binding [CARRIER] to parameter: [3]
2014-07-04 15:06:41,336 [main] [-] TRACE hibernate.type.descriptor.sql.BasicBinder - binding parameter [4] as [INTEGER] - [2]
2014-07-04 15:06:41,336 [main] [-] TRACE hibernate.type.descriptor.sql.BasicBinder - binding parameter [5] as [VARCHAR] - [website_3]
2014-07-04 15:06:41,337 [main] [-] TRACE hibernate.type.descriptor.sql.BasicBinder - binding parameter [6] as [BIGINT] - [4]
2014-07-04 15:06:41,338 [main] [-] TRACE hibernate.type.descriptor.sql.BasicBinder - binding parameter [7] as [INTEGER] - [1]
2014-07-04 15:06:41,342 [main] [-] DEBUG org.hibernate.SQL -
/* delete one-to-many com.ia.domain.Provider.contracts */ update
contract
set
provider_id=null
where
provider_id=?
Hibernate:
/* delete one-to-many com.ia.domain.Provider.contracts */ update
contract
set
provider_id=null
where
provider_id=?
2014-07-04 15:06:41,344 [main] [-] TRACE hibernate.type.descriptor.sql.BasicBinder - binding parameter [1] as [BIGINT] - [4]
答案 0 :(得分:8)
老实说,我不知道为什么,但如果您将CascadeType.PERSIST
(或更好CascadeType.ALL
}添加到@OneToMany
实体中的Provider
关系,它将按预期工作
这个小细节可能缺少Hibernate文档。
<强>更新强> 带有JPA2的EclipseLink 2.5.1似乎没有这个问题
第二次更新
在第2.9节“实体关系”中,JPA 2.1规范说: “如果孤立的实体是分离的,新的或已移除的实体,则orphanRemoval的语义不适用。”
我不知道您的相关实体是否已分离,但如果是,那么这不是错误:)
答案 1 :(得分:-3)
我也在说明这个问题。虽然它已被弃用,但以下使用在孤儿删除方面运行良好:
@org.hibernate.annotations.Cascade(org.hibernate.annotations.CascadeType.DELETE_ORPHAN)