[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2781) Changes to fields marked as non-updateable written to L2 cache

[Steve Ebersole (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28446 ] 

Steve Ebersole commented on HHH-2781:
-------------------------------------

The big issue is that of reattchment since it is quite possible that we do that have the old values in order to even know if properties changed, let alone what the un-changed values should be.  So another option here would be to just refuse to write the entry into the second level cache in these cases...

> Changes to fields marked as non-updateable written to L2 cache
> --------------------------------------------------------------
>
>                 Key: HHH-2781
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2781
>             Project: Hibernate3
>          Issue Type: Bug
>          Components: caching (L2)
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 3.2.6, 3.3
>
>
> When the value a field marked as update="false" is changed, that changed state is written to the L2 cache.  This occurs at least on reattachment, but I assume it also occurs for managed entities (need to verify).
> Viable solutions include:
> 1) disallow this combination (cached + non-updateable, non-generationed properties)
> 2) implicitly treat these properties as generated.
> Workaround is to mark these fields as generated.

-- 
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