Fluent NHibernate Cascade - Which side?

In using Fluent NHibernate, I can't seem to find a good explanation of when you use the cascading option on the References side vs. the HasMany side.

What's the difference (if any) in mapping the following...

References(...).Cascade.All();

vs

HasMany(...).Cascade.All();

My question stems from a problem when saving a parent (root) entity. Once it's saved, I want to insure that all child objects are also persisted.

Answers


You put the cascade on the side that you are saving.

If you save the parent and want to cascade to the children, put the cascade mapping on the parent.


Need Your Help

Android - activity_main cannot be resolved or is not a field

java android google-maps

Previous people have had the same error message, but the solution has always been to remove or modify some import "android.R". I have no such import so I'm really lost

What does the `forall` keyword in Haskell/GHC do?

haskell syntax types ghc forall

I'm beginning to understand how the forall keyword is used in so-called "existential types" like this: