Re: [hibernate-dev] Hibernate 4.0.1: regression with @OneToMany(cascade = CascadeType.REMOVE)
No JIRA yet. Want to decide on general plan of action first.
Well really the trouble is that you are not managing the associations
in memory. I understand the behavior is surprising, but had you simply
cleaned up the Person reference from all its associations (as the JPA
spec says you have to anyway) you would not have gotten this surprise.
On Wed 18 Jan 2012 11:17:32 AM CST, Guillaume Smet wrote:
Hi Steve,
On Wed, Jan 18, 2012 at 5:42 PM, Steve Ebersole<steve(a)hibernate.org> wrote:
> This is unexpected and obviously unintended, but it is also clearly what the
> spec says should happen. I have asked the spec lead about some possible
> options that would probably still meet the intent of the spec (even if they
> violate the wording) and would be more "natural".
Thanks for your answer.
Yes, it's surely not the desired behavior.
Our applications don't rely on it so it's not that critical for us but
I'm pretty sure it's going to surprise users.
Do you plan to open a JIRA issue for this problem?
Thanks.
--
steve(a)hibernate.org
http://hibernate.org