I have exactly the same problem. In our system we do not persist our data on a record per record basis. We translate data from the domain to view models, make several changes to these view models which includes re-parenting changes. Changes to the view model is applied back to the domain and the domain is persisted to the database using nHibernate. I expect that cascade="all-delete-orphan" would indicate to the ORM that the current state of the domain must be persisted with cascade and that any orphans in the domain must be deleted from the database. However, when this operation includes a re-parenting operation NHibernate raises an exception that the record will be re-saved. We want the record to be saved with the new parent.
Paladin_za has a valid reason for logging this as a bug. I my opinion this IS 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 -~----------~----~----~----~------~----~------~--~---
