On Wed, Oct 24, 2012 at 3:13 PM, Josh Earl <[email protected]> wrote:
> Thanks, Ramon. You are right--we want to use a different connection for > each customer. Issues like caching are exactly what I'm concerned about. > The worst case scenario I can think of is that making this change causes > subtle breakage that goes unnoticed in our low traffic staging environment > and then causes cross contamination of client data when deployed to > production. > If keys are unique accross databases then there should not be any problem. > My understanding is that implementing the IConnectionProvider interface > allows connections to be switched on a per session basis. But if the > sessions are using the SessionFactory as a cache, that only solves part of > the problem. I'll have to look into that more thoroughly. > A session always behaves as a 1st level cache caching al retrieved objects within that session. The 2nd level cache is not enabled by default and this caching objects across session. You probably are not using 2nd level cache. -- Ramon -- 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.
