I'm noticing an excessive number of updates in my system... When running profiler I'm seeing objects being updated that have definitely not been changed, IE their certifiably 'clean'.
--------------- // Save / update new objects... This is necessary because the next call will need those objects to run it's calculations. session.SaveOrUpdate(glBatch); // This will load all historic transactions, then use them to calculate balances... However the historic transactions are NOT // modified. glBatch = glBatch.ApplyPaymentsFromNewToHistoricTransactions(DomainEnums.ProcessHistoricTransactions.Both); // Save the new records / updated records... However it also issues updates for everything we just read, including // items that have definitely not been modified. session.SaveOrUpdate(glBatch); session.Flush(); tx.commit() ------------------------------ Any ideas? How would nHibernate determine that these items are dirty? Thank you, Gary -- 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.
