http://nhforge.org/doc/nh/en/index.html Section 9.4 and 9.6.
2011/4/26 Oskar Berggren <[email protected]>: > 2011/4/26 PLen <[email protected]>: > [...] >> It is almost as if NHibernate checks everything it got back from the >> query to see if any of the objects are different, regardless if they >> are attached to the object being sent in for the update. >> > > That is exactly how NHibernate is designed to operate. > > For instances that are loaded using a session, the session will try to > persist any modifications made to those instances during FLUSH phase, > which can happen at different times during the session lifetime. More > can be said, but this is covered by the reference manual. > ISession.Update() is used for making the session aware of an instance > that was loaded from a _previous_ session - i.e. load in one session > and perform changes in another. So if you load and perform changes on > the object in the same session, you should not call Update() on it. > > /Oskar > -- 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.
