[
https://issues.jboss.org/browse/ISPN-9369?page=com.atlassian.jira.plugin....
]
Galder Zamarreño resolved ISPN-9369.
------------------------------------
Fix Version/s: (was: 9.4.0.Final)
Resolution: Won't Fix
We won't fix this. The problem is that you could add entities into the DB and then
execute a query in the same transaction. The query result could be affected, and if you
cached = shared the query result, you'd be exposing an uncommitted entity
Non transactional query cache only cache results if transaction is
committed
----------------------------------------------------------------------------
Key: ISPN-9369
URL:
https://issues.jboss.org/browse/ISPN-9369
Project: Infinispan
Issue Type: Bug
Components: Hibernate Cache
Affects Versions: 9.3.0.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
{quote}Local query caches are not populated if the transaction is not committed.
The same test case works on hibernate 4.3.11
Our scenario: Read-only services that only execute queries and never commit the
transaction. It should still be possible to use/configure hibernate/infinispan to cache
the results, regardless the transaction state.{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)