I should also mention to clarify further, I have the use case where the instances I load are effectively all detached from any session. I do this intentionally as it feeds my WPF application. Then when I am ready to save after some changes have been made to the instances and constituent collections, I would reattach all to a new session. There are moments when that happens when the composition of collections would then be different. So there needs to be some reconciling between the two. I had to take some steps in countermeasure with EF apparently; not sure if FNH is any more or less transparent under those conditions.
Thanks! On Friday, June 6, 2025 at 11:29:51 PM UTC-4 Michael W Powell wrote: > Hello, > > Now that I feel I have sorted most of the major concerns and but for a > couple of lingering desires for reference conventons and what not... > > Now to one burning question, how to handle synchronizing with persistent > collections. What do I mean by that. > > I am pretty confident that new instances would simply be inserted and > existing instances be updated, as per usual. > > But what happens with non-existent instances. That have been removed from > the loaded and/or newly attached instance, and that still exist in the > persistent store? > > The issue I was findingwith EF, for instance, these instances required > manual intervention, or I had not discovered the EF policy making that > issue transparently resolved at the ORM level. > > Does it make sense? Much appreciated any insights. > > Best, thank you, > > 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/fluent-nhibernate/f395cf86-b000-48e4-881b-ecedbac6bf8cn%40googlegroups.com.
