Hi all,

I get this error:

Flush during cascade is dangerous - this might occur if an object was deleted and then re-saved by cascade

when I try to delete a child. The child and the parent are associated using a bi-directional association as follows:

<set name="child"
table="childTable"
cascade="save-update"
inverse="true"
>
<key column="parent_id" />
<one-to-many class="ChildClass" />
</set>


the child has a many to one reference to the parent as specified in the documentation.

In my unit test, I create the parent, create the child and associate the child with the parent. All this works fine. Then when I am done and ready to clean up the objects used in my test, the deletes fail and give me the error above. It seems from the parent child section in the documenation that I should be able to delete children fine this way.

Anything I should be looking for?

Thanks

I am using HIbernate 2.0.3. Basically following the exact configuration used in the parent child section in the documentation.

This faq:Hibernate throws: Flush during cascade is dangerous.
This almost always happens because you forgot to remove a deleted instance from an association with cascading save enabled. You should remove deleted objects from associations before flushing the session.

ashoknan, thanks for the reply. I tried that and it worked.

So when I am deleting the child, I should remove it from the association collection in the parent, save the parent, then delete the child.

parent.getChildren().remove(child);
session.save(parent);
session.delete(child);


///commit transaction....

The issue for me is that one session retrieves/creates the children and another session does the delete.

Thanks again..

>>The issue for me is that one session retrieves/creates the children and >>another session does the delete.

What is the issue here..it similar to what we do in normal transaction processes.

this example is a one-to-many association, how about many-to-many?????

Do I need remove the child of the Collection?
parent.getChildren().remove(child);

To do this, do I have to implement both equals and hashcode methods?

// Can I do only like this?


thanks a lot...

Yes, you'd better implement both equals() and hashcode(). I have checked on my .java files generated by hbm2java and found out that classes having one-to-many relationships with other classes (that is: these classes play the Parent roles in one-to-many relationships) all have implement both equals() and hashcode().

I get the same error