[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-404) Caching problem with same class mapped in many sessionFactories

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sat, 18 Oct 2003 6:25 AM

This is an interesting observation. I'm half inclined to accept your patch. OTOH, it seems to be a problem specifically with the JCS cache architecture. (For example, it would not affect the new HashtableCache.)  Note that we are de-emphasizing JCS!

Anyway, I'll give it some thought when I do the distributed cache stuff with Bela, but for now this kind of stuff -can- actually be handled in the pluggable cache layer by passing properties, etc.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-404


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-404
    Summary: Caching problem with same class mapped in many sessionFactories
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: WON'T FIX

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: William Drai

    Created: Wed, 15 Oct 2003 6:20 PM
    Updated: Sat, 18 Oct 2003 6:25 AM

Description:
I want to map the same class in two different sessionFactories using two different databases.
As the cache region is defined only by the class name, the cache is not able to differentiate instances of the same class with the same id in different databases.

I have made a patch for Hibernate 2.0.3 which just add a new parameter 'cache-region-prefix' in the session factory configuration and it works perfectly.

As the caching system is completely being refactored, it would be really cool if this simple fix was included in the refactoring.


Thanks.
William



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira