Not sure if this is something i'm doing or by design. When I save a parent object, it cascades the saves down. However, in the event of an error, it saves some of the objects in the hierarchy, but not others (the objects it errored on). I would assume normally that the entire save would have been in a transaction, so that either it all saved or nothing. Is this not the case? Do i have to explicitly put my objects into a transaction so that a cascade save is atomic?

Thanks,
Craig

You need to create the transaction yourself using Session.BeginTransaction. All actions should be in a transaction to be safe - in fact NHibernate 2.0 enforces this.

Cheers,

Symon