That is exactly what we do in our domain to reassign a part object. So, lets say that we reassign one child and remove a second like below
parent.Remove(child1) child.Parent = newParent newParent.Add(child1) parent.Remove(child2) child2.Parent = null Now, with NH's mapping set to cascade="all-delete-orphan" one would expect that child2 is deleted from the database and child one is persisted with a new foreign key for newParent. Instead NH raises an exception that indicated the record will be re-saved. As I see it, I want the record to be re- saved, with a new foreign-key. I see this as a bug and think that paladin_za rightly logged it as a bug. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
