[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2224) executeUpdate causes coarse cache invalidation

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Patrick Kranz commented on HHH-2224: ------------------------------------ Hi you two, I don´t really understand what the problem is you guys are experiencing. The blog entry you mentioned (http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic) explains why Hibernate behaves like it does. Basically it is because if you execute an update on the database Hibernate has no way of knowing which objects are obsolete. So, it invalidates the whole cache region. The other option would be to reload all the objects in the cache but this will happen anyway if you ask for those objects again since the regions is invalidated. So in my opinion, the behavior as is, is the preferred one. Regarding your three options: - If you know the ids of the objects you want to modify, you don´t need a bulk update operation. You can retrieve the objects from the 2nd level cache and manipulate them directly. Since they are in your cache no DB round trip is needed. The changes are in your cache and all is fine. - If you start invalidating the objects yourself you will forget it somewhere, trust me, and you will end up with hard to find bugs or stale data but it will definitely be worse than the "performance loss" of another DB round trip. - again, in this case, why not load the objects yourself and do the modification. seems like you are loosing yourself in the old "for someone with a hammer, every problem looks like a nail"-paradigm ;-) Best regards, Patrick -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira