I think nhibernate by default will update the version (for concurrency) field when you add/remove items from a child collection (the two child inserts). It can be disable by adding optimistic- lock="false" to the <set/> element in the mapping file.
If you set optimistic-lock="false", then add/remove children from the collection and don't change any fields on the parent, then nhibernate probably won't update your version column on your parent table. This may or may not be what you want depending on how concurrency should work in your particular application. Rob On Jan 18, 9:03 pm, Graham Bunce <[email protected]> wrote: > /bump > > Any comments? Why is the unnecessary (as I understand it) UPDATE > being generated by NH? -- 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.
