Hi guys,

I'm working with a long running session which contains all my required
data. Further, I use level 2 cache intensively, to cache that
information. I let my user edit this data directly using UI controls.

The user can decide to cancel the modifications, which I though I'd
easily solve with performing a ISession.Refresh(..) on the aggregate
root of the changed entity.

However, it turns out that Refresh(...) always goes to the database to
refetch the data, even if the data is available in second level cache
(tested that the data is there using a second ISession, which returned
the data without a database hit).

Is there a way to refresh entity from data in the second level cache?

I don't want to use Evict+Load, as I will then get a new instance
(Refresh(...) updates the same instance).

Thanks

-- 
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.

Reply via email to