Hi Everyone,

I need to implement parent-child relationship and I have a question.

According the Parent Child Relationship documentation, every time the application add/update/delete the child, the application requires to update the parent too (just the object not the database).

I have to design a heavy transaction process and all this process will do is insert/update/delete either the parent or child and save the information back into the database, I want to know will it be an disadvantage in future if the transaction process just load up either the parent or child, performs all the necessary transactions, save/update/delete the objects and flush them back to the database without updating child or parent relationship in object side (not the database), close the session, and move on to the next process. Will I have an disadvantage of doing this?????

Vivian Fonger