Have a setup with NHibernate 2.1 and mapped classes that all implement versioning. When getting an object from the session (using get) it would normally return the version in the session cache if it exists or otherwise check the second level cache for the data from which to construct a new instance (which then ends up in the session cache). By calling session.Refresh(o, LockMode.Read) you can force the refresh to bypass the caches and get the absolute up to date information on the object.

My question is this, I have loaded a great number of objects in the session to display several weeks of flying activities (say legs). Then when I change and save a particular flight using another sesssion (or from another computer) I would need to refresh this information. However, when calling the ICriteria query again for the same period, I would see the up to date information for any objects that are newly created in the period, but the existing legs still contain the old information (from the session cache)! Is there a way to force the query to update/refresh the session objects with the latest information when the version has changed, rather than returning the old info? The SQL query that is fired contains the version numbers but somehow that does not trigger a refresh??? So I quess the question is how do I prevent my session cache to get stale (as far as I know you can only set expiration times on 2nd level cache) Now I have to clear the complete session.cache before calling the query again (which seems a bit too dramatic)

It sure is interesting to post things on a forum and not having anyone who has the slightest bit of information on the matter. So I have to assume that either my question is so blatently stupid that nobody bothers to reply, or so badly worded that nobody understands... So can anyone tell me or ask me what wrong assumptions are into play here? Have only been working with NHibernate for a year so cannot claim to be the expert ;-)

Hi tderoo,
Did you find a solution to this problem ?
Would be very helpfull to me.
Thanks

No unfortunately this problem is still occuring. It seems that NHibernate is very much developed with a web interface in mind where you just have a page whith the session at the beginning, make your changes, and save them. Then you just take a new session for the next action. This does not combine very well with the forms approach where multiple screens could be amending the same information over a longer time span. At the moment I start to rely more on the 2nd level cache and sometimes just clear the current session before refreshing even if that feels like a waste of resources. Still waiting for the guru who could tell me a bit more :-) So sorry but no answers yet...