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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] Vladimir Kralik commented on HHH-2224: -------------------------------------- Hi all, I've similar problem, i need use createSQLQuery(SQL).executeUpdate(). It's have to be used because of lack of hint in Hibernate and also speed is important to me. Now I setup second level cache ( Ehcache ) and I was surprised, that there isn't objects in cache. Simple unit-test said, that second level cache is working, but when I put any createSQLQuery(SQL).executeUpdate(). between command, all caches were cleared. All means everything in all regions, including read-only caches. So regurally executing of "createSQLQuery(SQL).executeUpdate()" makes second level cache useless :-( I don't agree with Patrick : It's a time problem to read a thousands object into memory only for deleting it. But when I've a lot of caches (read-only objects), performance is going down, because each call "executeUpdate()" needs to invalidate every cache, and maybe there is a locking problems. I thing, that Hibernate should have options to switch off second level cache cleaning, when "executeUpdate()" is called. For me this means, that this piece of code should be configurable in some way. http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/trunk/core/src/... -------------- /** returns true if no queryspaces or if there are a match */ private boolean affectedEntity(Set querySpaces, Serializable[] entitySpaces) { if(querySpaces==null || querySpaces.isEmpty()) { return true; } ---------------- -- 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