[ http://jira.nhibernate.org/browse/NH-736?page=comments#action_14561 ]
Ayende Rahien commented on NH-736:
----------------------------------
more specifically, I am talking about it not being used for entities.
For query cache, it is used, but not when storing the entity data itself.
> Caching cause leaking of entities data from one session factory to another
> --------------------------------------------------------------------------
>
> Key: NH-736
> URL: http://jira.nhibernate.org/browse/NH-736
> Project: NHibernate
> Type: Bug
> Components: Core, Contrib
> Versions: 1.0.2, 1.2.0.Alpha1, 1.2.0.Beta1
> Reporter: Ayende Rahien
> Assignee: Ayende Rahien
> Attachments: add-cache-region-prefix-to-2nd-level-cache-2.patch, add-cache-region-prefix-to-2nd-level-cache.patch, add-session-name-awareness-to-2nd-level-cache.patch
>
> Assuming that I've an Employee #5 in two session factories, and caching is enabled, it is possible that data that was loaded in one session factory will be returned from the second.
> This is because the generated cache key is the same, and the cache space is shared in all implementations.
> Should use the session factory name to distingiush between the caches, since that will allow using the cache in distributed scenarios yet maintain the seperation between seperate session factories.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
