I have two classes Post (1) and Comment (n). The Comment has the following configuration :

Post.hbm.xml snippet:
...
<set name="comments" order-by="created desc" cascade="all">
<key column="post_id"/>
<one-to-many class="net.eyde.personalblog.beans.Comment"/>
</set>
...

Comment.hbm.xml snippet:
...
<many-to-one name="post" class="net.eyde.personalblog.beans.Post" column="post_id"/>
...

Delet Code Code:
....
session = sf.openSession();
session.delete(session.load(Comment.class, commentId));
session.flush();
session.close();
....

When I delete a post everythings work fine, the related comments are deleted, but when I delete a comment with the following code, I get the error :

net.sf.hibernate.HibernateException: Flush during cascade is dangerous -
this might occur if an object was deleted and then re-saved by cascade


1

page content: "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.
"

Does it means that I must choose :

* Cascade delete - Having more work to create the childs adding it to the collections and saving it separated.
* Cascade all - Having more work on deletion, having to get the associated 1 side of the relation from child, and removing from there, and deleting the child after all.

After all, I didn't get the message, since I'm deleting the side of cascade that should not thrown any cascade. The cascade is from the 1 side to the N side.

Isn't there any approache that allows me to cascade from parent to child (1 to n side), and even let me delete child without having to touch the parent collection (that contains the N side).