Team,

Is this how the cascaded save or update works.

(Assume that the abjects are new at it is all save).

Hibernate

Read the parent child document on the wiki. It should provide some pointers.

By wiki do you mean http://www.hibernate.org/37.html

If not, Please do forgive my ignorence and point me to the right place.

Also i have gone through the parent- child notes in the document (PDF version) and that does not give me enough insight as to how exactly it does work.

Regards
Suchak Jani

The reference documentation contains the "parent/child" chapter theses days, not the wiki. And is, with the other 100 pages of reference documentation, enough to understand this issue.

Christian,

I would really appreciate if you would point me to the right place for answering this question.

Why does hibernate do this (internally)
1. Save parent entity
2. Save child entity (with relating column as null)
3. Update the child setting the relating column to the parent

Because you forgot to set inverse="true" on the "many" end of your association. Read the parent/child mapping chapter, twice if neccessary.

Yes Christian,

That must is true, however in my case one Child can have many Parents.

Here is what i mean and i guess i will give you a concrete example.

There is a Address table, which has a Owner_Type and a Owner_ID. Now a Company could have Adresses, a Corporation could have Addresses, a Bank could have Addresses.

So for Company type Address.Owner_Type="Company" and Address.Owner_ID="Company_ID"
but for Corporation type Address.Owner_Type="Corporation " and Address.Owner_ID="Corporation _ID"

In other words Company has "one to many" with Address, but Address is not a "many to one" with Company as Address has "many to one's" with Corporation, Bank etc also.

However when saving, let's say a Company, for which Hibernate does have a one to many with Address.owner_ID related by Company_ID, why should hibernate do it in three steps , the second step being save address with Owner ID as null.

By the way i did read the document and i think i am clear on what it explains, however this problem of mine, that i describe above, is different and i hope it is not unique.

I still think that if i have a inverse on the "one to many" side that Hibernate should do this ::::
1. Save parent entity
2. Save child entity with relating column as parent