This question is regarding performance of an application using hibernate .

If i have a parent P (with cascade save-update to children C's ) .
If we have 1000 (new/dirty) children (already referred in P) .

And if we call save on Parent P , this tries to save Parent and 1000 Children of this parent.

In this case does hibernate use batch updates ?

or

Should we explicitly use batch update implementation in our code

like :



Thanks,

Kurt

Only if you have set hibernate.jdbc.batch_size property. In addition you should remove the flush call.



Farzad-

Did you read my post properly? .Can you just elaborate ?

Do you mean the save on Parent -> if it cascades saves on children by hibernate (is batch update implementation? ) ..


I did not get any thing out of your answer !!!!!

Thx,

Kurt

I give you more explanation. As far as I know Hibernate caches modified objects in a queue and save them when it is appropriate (if flushmode is auto). Therefore, when you have a parent and modified objects then hibernate will definitely look into batch updating if that property is set. however, something I missed from your original post was that there are new objects too. That still can work if the object's primary keys are not identity or anything for which hibernate has to go to database and come back with a value. If not, batch update still works.

Tell me if I am off the topic. I also have a feeling I have not understood your question.


Farzad-