[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=c...
]
Karl Smola commented on HHH-2224:
---------------------------------
Hi Stephan,
I have been experience exactly the same issues, details of my test case and my
observations are available in this post:
http://forum.hibernate.org/viewtopic.php?t=989568.
I noticed that this issue has been logged as an improvement, has the hibernate team
confirmed this is the intended behavior? I find it hard to believe that any application
that uses 2nd level caching is unable to use DML or SQL style bulk updates without
clearing the cache.
If it is the intended behavior then this bug need to be filed under documentation as I
found no references to bulk updates or second level caching.
Regards
Karl Smolka
executeUpdate causes coarse cache invalidation
----------------------------------------------
Key: HHH-2224
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224
Project: Hibernate3
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
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