Closed
Description
I faced a longer IsDirty run after upgrading.
NHibernate 3.3.1:
NHibernate 5.4.2:
The first question is, was there a bug in old implementation that now lead to this cascade?
Since the result of IsDirty is true in both cases, I can imagine that there is optimization potential.
The test case of IsDirty is there that we have a table which stores for every element a parent element (not lazy load). The children are as HasMany relation. We remove just near all elements, and this lead to this bad result.