[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c...
]
rajesh kumar commented on HHH-2224:
-----------------------------------
if you are computing the query inside java application the I hope you are using
org.hibernate.SQLQuery object fon r executing the query. In that case you could use any of
the following method to acheive the same thing.
SQLQuery SQLQuery.addSynchronizedQuerySpace(String querySpace)
Adds a query space for auto-flush synchronization.
SQLQuery SQLQuery.addSynchronizedEntityName(String entityName)
Adds an entity name or auto-flush synchronization.
SQLQuery SQLQuery.addSynchronizedEntityClass(Class entityClass)
Adds an entity name or auto-flush synchronization.
executeUpdate causes coarse cache invalidation
----------------------------------------------
Key: HHH-2224
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224
Project: Hibernate Core
Issue Type: Improvement
Affects Versions: 3.2.0.ga
Environment: Hibernate 3.2.0.ga, Oracle 9.2
Reporter: Stefan Fleiter
Attachments: bulk_testcase.zip, hibernate-3.2.6_p4.patch
I am developing an application and want to mix bulk-updates
with normal hibernate operations.
The bulk updates work fine, but invalidate the whole region and I've found
no possibility to prevent this.
There would be 3 options to improve:
- Invalidate only the modified objects if the ids where given as Query-parameters.
- Let me deactivate the invalidation so I can invalidate the affected objects myself.
- Transform the DML to a select to gather the objects to invalidate before executing the
DML
The reference documentation does not mention caching at all:
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct
The best documentation I've found is:
http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic
Maybe this could be added to the reference documentation...
I already posted this at the forum
http://forum.hibernate.org/viewtopic.php?t=966775
but did not get a single answer.
I've attached a testcase for this.
--
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