Is there any way to disable checking for stale child records when we
are not cascading updates?

That may seem an odd question, but we’re using NHibernate to build
hierarchies on retrieval and the security design we’re working from
calls for updates to happen for only a single level of the hierarchy
at a time, so we really don’t want to have to care about whether a
parent contains current children or not when we go to update the
parent; we just want to persist parent fields.  Our mapping files make
this clear to NHibernate by telling NHibernate not to cascade updates,
but NHibernate still does some amount of checking, which means that we
have to do a fair amount of unnecessary work.

Without debating the merits of not cascading updates (not much I can
do about same), is there some way anybody knows of to get the error
checking to be (what we think of as) consistent with our mapping
files?

Cheers


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to