In Hibernate you can call setReadOnly(true) on a query or criteria in order to tell Hibernate not to persist the object context (and therefore not flush the objects loaded in that query). Is this possible in Nhibernate? There doesn't seem to be this method or property and all searching I've done about flushing only some objects mentions multiple sessions and eviction...

Thanks,

Aaron

Aaron,

I am not sure if NHibernate.ICriteria.SetCacheable(System.Boolean) serves your purpose.

Regards,

Ken

Nope, cacheable is different. That allows you to decide whether or not the query itself is cacheable in the query cache afaik. It does not affect whether or not the objects retrieved by that query are kept in the persistence context and therefore flushed at the next flush.

I'm also confused as to why immutable objects are flushed... is that just for integrity's sake? Seems like something that should only be done in dev land a la asserts (it throws an exception anyways).

Is the only way to control flushing really to have two separate sessions? That seems like quite a hack to me for something that is done nicely in Hibernate.

Is this supported or not? Will it ever be?

It's not supported now but there isn't anything preventing it from being implemented.

Should I JIRA it? This would be a pretty big performance win for us and anyone else that uses large trees of read-only objects.

Yes, do it.