Hello everybody!

I use the following combination of Objects in Hibernate:
Order having a Collection (<set>) of OrderParameter objects mapped to it.

Now what I would like to do is to be able to delete an Order-object. Consequently removing all OrderParameters that it has among it. To do that I added a "cascade=delete" to the respective collection mapping.

Now what Hibernate does now is an "UPDATE OrderParameters SET order_id=NULL where order_id=?" resulting in that my database says that an OrderParameter may not exists without a parent.

Can somebody help me?! Did I get the Collection concept wrong? Or to I have to map the Collection in another way?

Thx, Tim

Deleting something from a collection generally only deletes the RELATIONSHIP between the parent and the child, not the child itself. If you want the behaviour where deleting from a collection also deletes the child try cascade="all-delete-orphan" or alternatively manually delete the child.

Ok, the following did help, and I don't really know why:
I added the "delete-orphans", after that Hibernate was still trying to set the Childs to NULL, ergo resulting in a Contraint-Violation.

Then I set the "inverse"-attribute to true and viola, it is doing what I expected it to do. So why is that?!

You didn't read the "Parent Child Relationship" chapter of the documentation. It was recommended before you clicked on the link to this forum. This is also helpful if you want to understand "inverse":

http://www.hibernate.org/155.html

Well, I did, but seems I didn't do it closely enough!
Anyway, thx for the help!