Some updated observations leading me to believe that somehow possibly cached instances are not being handled properly as would-be orphans.
https://github.com/nhibernate/fluent-nhibernate/discussions/750 That is, our internal logistics via ObservableCollection<T> are doing the right thing by removing the instance from the source NH provided collection, and nullifying the parent relationship correctly, at least as far as domain models are concerned. But when we turn around and signal SaveOrUpdate(...) to the session, we are finding the errors (see github discussion). So... is our recourse to run without cache, and do the delete reconciliation manually? This was the same with EF. Or if there is a better way of handling it that it just flows naturally with the ORM, we are open to learning about it. Best... On Sunday, June 15, 2025 at 5:50:38 PM UTC-4 Michael W Powell wrote: > Hello, > > Would someone mind addressing this question? Basically just needing to > know how string NH is at dealing with the dirty collection reconciliation > process; adding, updating, and especially deleting child instances, as > appropriate. > > https://github.com/nhibernate/fluent-nhibernate/discussions/750 > > Or the SO, either way. > > > https://stackoverflow.com/questions/79666373/nhibernate-saving-dirty-collections > > Thanks! > > Best regards, > > Michael W. Powell > -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To unsubscribe from this group and stop receiving emails from it, send an email to fluent-nhibernate+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/fluent-nhibernate/bbcce60f-50cb-4748-b6b0-a7c354b8200an%40googlegroups.com.
