Hi everyone,

I've got an object A that has a set of object B that itself has a set of object C
Both sets have the option cascade="all-delete-orphan"

Each A can have up to 10000 object B in its set. And each B have 3 object C in its set.

So when deleting several A object, it's like deleting couple of 30000 linked objects.

Hibernate loads every C object and then fire a delete request for each of them. It takes a very long time and put a very high load on the DB.
If I trigger it on the DB itself it's done instantly (with the right casscade options)

I was thinking of using the batch-size option, but still it's not going to be as fast as the db.

Is there any other way to speed up this deletion process??

regards,
nodje

If you really need to delete thousands of objects, I think best way would be to simply use session.connection, and use a few jdbc statements on the returned jdbc connection...

There are some tips in the manual on deleting that might help however if you really need to do this in an OO way

http://www.hibernate.org/hib_docs/refer ... shotdelete

Well this is a db cleanup operation that the user will launch once a year.
Even though, there'll be so much element that it will take ages. So I need to speed up the process anyway.

Using jdbc statement seems to be a very fair option, the only question is:
Will this keep my 2nd level cache (ehcache) synchromized or will I have to do it manually?

(I don't even know if it's possible to tell the cache some object disapeared from the db, I thing only emptying the cache via evict() is possible)

regards,
nodje

You have to manually evict the cache.

Right, if I do evict them from the cache, the concerned objects won't be available if some process tries to load them.

But if I don't do that in an OO way, it's like an external process modifying the DB. And resynchronizing the cache might no be enough. HIbernate itself need to be resynchrinized. Some process might be using some of the object that are going to be deleted. In this case an instance of a deleted object might be left in memory.
Am I right here, or is the evict() method taking care of the in-memory object instances??