[
https://issues.apache.org/jira/browse/OPENJPA-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853249#action_12853249
]
Rick Curtis commented on OPENJPA-1603:
--------------------------------------
I didn't notice this before, but it looks like I fat fingered my commit message
for the 2.0.x branch. Here is a link to the real commit --
http://svn.apache.org/viewcvs?view=rev&rev=928968
> Decouple the QueryCache from the DataCache
> ------------------------------------------
>
> Key: OPENJPA-1603
> URL: https://issues.apache.org/jira/browse/OPENJPA-1603
> Project: OpenJPA
> Issue Type: Improvement
> Components: datacache
> Affects Versions: 2.0.0
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Fix For: 2.0.0
>
>
> In doing some testing I have found that there is a valid use case where one
> would want to use the query results cache (openjpa.QueryCache), but not the
> DataCache. I'm using this JIRA to remove the dependency between these two
> caches.
> The gist of this change is that the QueryCache will now talk with the
> StoreContext to see if the results of a cached query are contained in the L1
> cache OR by any of the DelegatingStoreManager's cache. The default
> JDBCStoreManager and the XMLStoreManager both do not have any concept of a
> cache and will always not have any cached results.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
