You probably have a problem in your mappings. Nullable db columns that are getting a value because they are non-nullable in your mappings. Check out the GhostBuster.
Here (http://nhforge.org/blogs/nhibernate/archive/2008/10/20/how-test- your-mappings-the-ghostbuster.aspx) and here (http://jfromaniello.blogspot.com/2010/02/nhibernate- ghostbuster-version-11.html) On Apr 23, 3:00 pm, gary lucas <[email protected]> wrote: > 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 > athttp://groups.google.com/group/nhusers?hl=en. -- 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.
