]
Romain Gonord commented on HHH-7004:
------------------------------------
I agree for the select following the update, but what about the next ones ?
The idea would be :
getBylabel -> put in cache version 1
update
getByLabel -> put in cache version 2
getByLabel -> get version 2 from cache
Query cache is getting weird after an update into a single
transaction
----------------------------------------------------------------------
Key: HHH-7004
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-7004
Project: Hibernate ORM
Issue Type: Bug
Components: core
Affects Versions: 3.6.9, 4.0.1
Reporter: Romain Gonord
Assignee: Strong Liu
Attachments: testHibernateEhCache.tgz
Hi all,
I'm using hibernate 4.0.1 and I'm facing a strange behavior. I can reproduce it
with hibernate 3.6.9.
I have an entity (integer id, string label) with query cache and level2 cache activated.
If I load this object by its label, i get one select in the log and every following
getbylabel doesn't produce any select query.
As soon as I modify my object (that leads to an update query), each time I call the
getbylabel, i get a select.
By activating hibernate log, i can see that there is something strange with cache
timestamp, which lead me to the following bug report :
https://hibernate.onjira.com/browse/HHH-5210.
Any idea ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: