I have an NHibernate session that is alive for the entire asp.net session. whenever I make changes to the properties of my NHibernate objects without saving these changes NHibernate always issues an update statement anyway when I try to reload the object. Why?

Hi Nissim,

That'll be "transparent persistence" at work. The idea is that all changes made to objects will be persisted when a flush occurs, which happens automatically under some circumstances (most notably before a select is executed) even if you disable auto-flush.

It is possible to prevent through some fiddling around with the IsDirty callback in an interceptor, but it's not entirely straight forward.

If you want to know more about transparent persistence you can find plenty of info in the Hibernate forum and Google.

Cheers,

Symon.

Flush being called automatically is a pain in the ass. How come when we turn off auto flush it still auto flushes? That doesn't make any sense at all. surely there is a reason for it. But what is it?

Will random flushes even occur if you set ISession.FlushMode to FlushMode.Commit?

Of course it doesn't make sense. How do you turn off the autoflush? Using FlushMode.Never or FlushMode.Commit should be enough. The reason for autoflushes is that NHibernate wants to give accurate results for queries by default.



No, they shouldn't.

Thanks sergey. I was scared there for a second.