merge_s.rottem wrote:
I believe that this is the expected behavior.
It looks like you are modeling a parent/child relationship where X is the parent and Y are the children. If you want the child item to be deleted when it is removed from the collection I think you can use cascade="all-delete-orphan" - this should also delete the child if the parent is deleted.
Symon.
This seems correct...
I've read that in some applications, the "Delete" command only sets a bit "isDeleted" in the table, to be able to trace changes. Is there a "best practice" to achive this function?.
//lasse