From: Steve E. (JIRA) <no...@at...> - 2006-07-14 20:58:01
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1911?page=all ] Steve Ebersole reopened HHH-1911: --------------------------------- > evict has no effect with ReadWrite cache Strategy > ------------------------------------------------- > > Key: HHH-1911 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1911 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3 > Reporter: Michael Kopp > > > I first found this when my own Persister informed the EntityUpdateAction to invalidate the cache. > persister.isCacheInvalidationRequired() > The EntityUpdateAction dutifully calls evict on the Cache, but that did not effect the cache state in any way. I looked into it and found that evict is a noop in ReadWrite Cache. > This breaks the consistence. The item is still in the cache after the update, unchange even after the transaction completed. > The next load will return a wrong state!!! > I digged a little more and found that the same thing happens on a delete too. the EntityDeleteAction calls evict but of course nothing happens. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |