Hi Fabio The bug is due to the fact that the expected behaviour for one case breaks the expected behaviour for another.
You can't support both situations in one configuration meaning that the bug is in actual fact in the functional specifications. cascade=all-delete-orphan <-- allows orphan deletes, but breaks re- parenting cascade=all <-- allows re-parenting, but breaks orphan deletes >From my understanding I would like cascade=all-delete-orphan to be intelligent enough to handle orphans as orphans and children with new parents not as orphans (they have parents, just not the same ones) Make sense? On Sep 10, 8:10 pm, Fabio Maulo <[email protected]> wrote: > I would like to know why this is a bug before have an answer and after you > have read about expected behaviour. > > 2009/9/10 Paladin_za <[email protected]> > > > > > I've logged a JIRA issue and attached unit tests demonstrating the > > problem as per > > >http://nhforge.org/blogs/nhibernate/archive/2008/10/04/the-best-way-t... > > >http://nhjira.koah.net/browse/NH-1962 > > -- > Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
