Hibernate requires a load, create, or store operation to occur before a delete can be issued. That means, I think, a SQL SELECT or INSERT has to happen before a SQL DELETE can be issued in the background. Isn't this SQL SELECT or INSERT reduntant since most of the times in the application you know that what you are deletind exists in the DB? Does't application performance hurt.

Thanks

Jamal

But Hibernate has to cascade operations and run other lifecycle methods. It has to have an object in the Session before the object can be deleted. This is of course bad for mass deletes, which is why you should not execute mass operations (including UPDATEs) with Hibernate, but use direct SQL calls. Usually, this is a rare case in most applications that use object/relational mapping.

Actually, it is quite acceptable to do:



So, in fact, no SELECT is needed.

Note that what I just said does not contradict what Christian said.