What happend when I will write "inverse=true" in the child class mapping instead of parent class mapping.

For example:
An organization have many employee and the mapping file contains following mapping:

1. Employee.hbm contains:

<many-to-one name="organization" insert="true" update="true" inverse=true column="ORG_ID" lazy="false" fetch="join" class="Organization" not-null="true"/>

2. Organization.hbm contains:

<set name="employees" lazy="false" fetch="join" table="employee" cascade="all">
<key column="ORG_ID"/>
<one-to-many class="Employee" />
</set>

Thanks in advance

Umashankar.

From the Hibernate manual:

"What about the inverse mapping attribute? For you, and for Java, a bi-directional link is simply a matter of setting the references on both sides correctly. Hibernate however doesn't have enough information to correctly arrange SQL INSERT and UPDATE statements (to avoid constraint violations), and needs some help to handle bidirectional
associations properly. Making one side of the association inverse tells Hibernate to basically ignore it, to consider it a mirror of the other side. That's all that is necessary for Hibernate to work out all of the issues
when transformation a directional navigation model to a SQL database schema.
The rules you have to remember are straightforward: All bi-directional associations need one side as inverse. In a one-to-many association it has to be the many-side, in many-to-many association you can pick either side, there is no difference."

Ken