[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6680?page=c...
]
Ben Hood commented on HHH-6680:
-------------------------------
The issue appears to be that the update timestamp is incorrectly set by calling
preinvalidate/1 instead of invalidate/1 on UpdateTimestampsCache, as indicated in this
patch:
https://github.com/0x6e6562/hibernate-core/commit/615aa049e7a557d4a8506a0...
I don't know what the knock on effect of this change is though.
2L caching appears to ignore collections
----------------------------------------
Key: HHH-6680
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6680
Project: Hibernate Core
Issue Type: Bug
Components: caching (L2)
Affects Versions: 3.6.7
Environment: 3.6.7 on Derby 10.8.1.2 and Oracle 11g
Reporter: Ben Hood
I have a scenario where a (read-mostly) mapped collection is eagerly loaded with the
parent object, but when I retrieve the graph, the 2L cache appears to get ignored and the
data is hydrated from the DB.
I have created a test case to reproduce this issue as a runnable Maven project on Github
:
https://github.com/0x6e6562/hibernate_2L
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira