From: <leg...@at...> - 2003-10-30 15:08:16
|
The following issue has been updated: Updater: Mikheil Kapanadze (mailto:mi...@di...) Date: Thu, 30 Oct 2003 9:07 AM Comment: The attached QueryCache.zip file contains patch for this issue Changes: Attachment changed to QueryCache.zip --------------------------------------------------------------------- For a full history of the issue, see: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-436&page=history --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-436 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-436 Summary: Divide QueryCache in multiple regions Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: core Assignee: Reporter: Mikheil Kapanadze Created: Thu, 30 Oct 2003 9:06 AM Updated: Thu, 30 Oct 2003 9:07 AM Description: Hibernate uses one instance of query cache for all cached queries. In some cases user may want to store query results in the different caches instead of using "main" one. Here is a description of the major changes 1. There were 2 caches in QueryCache.java - query cache itself and timestamp cache. The last one was moved to the separate class, because we didn't divide that cache. 2. cacheRegion property was added to the Query and QueryParameter classes 3. There is a new method, getQueryCache(String cacheRegion) in SessionFactoryImpl. It returns query cache, stored in the internal map or creates new one and puts it there. It also destroys all these caches in the close() method. 4. There are some minor changes, too. For example, default query cache's region name was changed to net.sf.hibernate.cache.QueryCache. This was done as object cache's region name equals to classname and there may be conflict in naming if someone has QueryCache class (without package) in his code. --------------------------------------------------------------------- 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 |