Your expectation is not correct. If you Save a transient instance and then modify it, it will be saved with the original values first and then updated. You'll need to make sure you don't call save on an invalid object.
Diego On Wed, Mar 24, 2010 at 15:29, ragamuf <[email protected]> wrote: > I created an entity via the default constructor and added it my unit > of work immediately via Session.Save. I then made subsequent changes > to this entity prior to commit. I would have expected a single insert > with the changes aggregated. However, what I see is an insert with the > default profile followed by an update with the subsequent changes. The > insertion fails because of null constraints violations due to an > incomplete profile. > > Why is my expectation of a single insertion not correct? Are changes > to a transient not tracked? > > P.S The POID was controlled by the application via a HILO so there is > no immediate jump to get the Id. > > -- > 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]<nhusers%[email protected]> > . > For more options, visit this group at > http://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.
