In my c# winform application I have a form with a list of tasks that users can work on. When a user begins working one, the row is updated to reflect this. The application tries to refresh the list of tasks once a minute, but updates aren't being reflected in the objects returned from queries in other sessions. So, other users are not seing the fact that a task has been updated by another user (and session).

I have tried using SetCacheable(false) and SetForceCacheRefresh(true) but I still get old copies of the objects.

I get this using both 1.0.2 and 1.2b.

I tried manully evicting the object returned from the prior query and this works for the main object, but dependent objects returned in collections are not. So, I imagine I would need to evict these as well. Doing it this way seems kind of messy though. I know a Session.Clear() could be done, but this seems extreme.

Below is the snippet of code I am executing. So, what am I doing wrong? Is there a better approach that I just missed?




I also tried switching query cache off but this didn't have an effect. I also switched to the prevalence cache and set the expiration to 1 second. This didn't seem to help either.[/code]

Are you Flush() the sessing changes?

I am flushing and committing the changes in Session A. I went to db and verified the changes where there and they are. So, if the objects had already been loaded into Session B, then the updates are not showing up, unless I force a refresh of each object.

Well, that is to be expected, isn't it?

I understand the updates would not show up automatically and that I would have to initiate retrieval of changes. But I guess I expected that if I did a query, that would get the changes. If I understand what you are saying, then I can't use a query to refresh object state from the database and I have to evict all objects to be refreshed (and dependent objects), call session.Refresh() on the objects or call session.Clear() (sort of the nuclear approach). Is this what you are saying?

Yes, it won't change the entity under you, because this may cause a lot of very hard to find issues.
What you seem to want is to get a new _copy_ of the data whenever you pull it out of the query.
If that is the case, you need to Evict() those entities.

Evict is a great thing for multi-user environemts. But if we have one object changed in Query collection containing, say, 100000 items, in session A (PC#1) why we should evict all of these items in session B (PC#2) from cache to make sure we show the latest changes on screen? Is that possible to supply version control here so all changed entities (with DataRowEntity.Timestamp>CachedEntity.Timestamp) will go to hydratedObjects and re-loaded from the IList DoQuery? Sorry if missed something