Hello, So, I am encountering the classical exception, PropertyValueException.
"Contributing" to this exception, I am working with a parent/child bidi relationship. I am deleting some child instances. Possibly needing to reload the parent. Then I am also touching the parent, changing its name, in the same sequence, though a separate session transaction. This is where I encounter the exception. As far as I can tell, although there may be database null or not null expected, we need to "fool" the check into thinking that null is acceptable, at least in the interim while children are being added or removed. That appears to be the prevailing recommended workaround, but I'm not sure I understand why, especially when cascading "all delete orphans" is enabled, i.e. as some have suggested cascade "all". But I'm not sure I understand the reasons why for the disconnect. References: http://nhibernate.info/blog/2009/08/23/part-5-fixing-the-broken-stuff.html Regards, Michael Powell -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
