Hibernate version:2.1.8

Hi,

I have a really large "tree-like" object model wich includes many one-to-may mappings with cascade="delete" option.

My problems are starting when i'm trying to delete the "root" object. While Hibernate is performing cascade deletes, it's actually retrieving all object model into the memory. It is very bad for me - from memory consumption and performance point of view. Is there any way to get around this?

May be the framework can (or i can cause it) build delete statements based on parent ID's instead-of traversing all children and deleting them explicitly?

Thanks a lot!
Michael.

I still didn't get an answer ... anyone? Hibernate team?

Thanks.

hibernate2 needs to load the object to apply the required lifecycle and cascades.

in hibernate3 you can use batched deletes and/or on-delete="cascade" which can utilizes database-level ON CASCADE DELETE (Be aware that this feature bypasses Hibernate's usual optimistic locking strategy for versioned data)

Thanks!
Look like we are going to upgrade to Hibernate 3.