Hi, I can understand setting cascade="delete" or cascade="none" on a one-many or many-one relationship.

With cascade="delete" on parent's mapping file, children gets deleted when parent is deleted.

With cascade="none" on parent's mapping file, nothing is done - children remains as orphan.

But, what's meant by:

cascade: "save-update" ...

there's nothing on children to be "updated" when parent's updated? The only thing to be updated is FK/PK field (foreign/primary key).

Thanks.

Well, someone please correct me if i'm wrong but what I understand this to mean is:

(assume i already have a parent object that was loaded from Hibernate)

Child child = new Child();

parent.Children.Add(child);
child.Parent = parent;

if the Parent defines it's children 'set' with cascade="save-update", then the child object will be automatically persisted to the database at the next commit.

if save-update is not specified, then (if I am reading the docs correctly) you would have to explicitly call save on the child object in order to persist it to the database.

crystal clear. Thanks