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

[Steve Ebersole (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37677#action_37677 ] 

Steve Ebersole commented on HHH-2224:
-------------------------------------

Vladimir, there is a significant difference between Hibernate allowing a certain (incorrect) behavior and developers achieving this behavior by "[finding a] path which by-pass this barrier".  Namely in the first case the implication is that Hibernate supports such a (incorrect) behavior, condones it even.  How do you correlate a read-only cache and things that can be updated?

Ioannis, as I said I am not ruling out a pluggable strategy where developers could themselves choose this behavior.  There is, again, a significant difference between Hibernate providing the option to enable this behavior via switch etc versus it providing the ability for developers to plug in this behavior.  And trust me, if we go this route, we will see bug reports here about how Hibernate served up incorrect cached results because the user developed a bad pluggable "bulk operation cleanup" strategy.  I assume I can send them to you for a lecture on how they "are fully responsible"? ;)

> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira