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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c... ] rajesh kumar commented on HHH-2224: ----------------------------------- Hi All, I have found a solution to the problem described. Hibernate provides a <synchronize> tag to specify what all are the tables that are affected becuase of the bulkupdate. If we are specifying the <synchronize>with table name hibernate only invlidate the cache of the table present in the synchronize table.This will avoid clearning of all the cache regions including the read only cache. For achieving this, <synchronize> should be added to the <sql-query> during a bulk update or a delete. Eg: <sql-query name="queryname"> <synchronize table="tablename"/> update tablename set value = ? </sql-query> The synchronization should be done on the affected tables because of the update. There can be one or more synchronize tags within the same block depending on what all tables got affected. This will result in cache invalidation of only those tables which are synchronized; otherwise the entire cache region is invalidated. Note: Hibernate does a flush of the pending data for synchronized tables (from insert/update queue) before actually doing the synchronization. So the flush is triggered automatically for those data in the insert/update/delete queues where the affected tables are synchronized. We could get this documented in hibernate reference documentation. -- 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