[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-5853) Problem loading cachable collections defined with a property-ref key with a versioned owner
Steve Ebersole (JIRA)
noreply at atlassian.com
Thu Jan 20 10:33:05 EST 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Ebersole updated HHH-5853:
--------------------------------
Description:
If an entity defines a collection with a property-ref based key as cacheable, there is a problem loading said collection and putting it into its second level cache region. The issue appears to be due to the incorrect "key" used to locate the owning entity; it tries to use the referenced property value instead of the corresponding id value.
Workarounds include:
* Migrating away from property-ref and normalizing the data
* disabling caching on the collection
* disabling versioing on the owner
* disabling versioning on the collection ({{<set ... optimistic-lock="false">}})
was:If an entity defines a collection with a property-ref based key as cacheable, there is a problem loading said collection and putting it into its second level cache region. The issue appears to be due to the incorrect "key" used to locate the owning entity; it tries to use the referenced property value instead of the corresponding id value.
> Problem loading cachable collections defined with a property-ref key with a versioned owner
> -------------------------------------------------------------------------------------------
>
> Key: HHH-5853
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5853
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Reporter: Steve Ebersole
> Assignee: Steve Ebersole
> Fix For: 3.6.1
>
> Attachments: CollectionIssue_TestProgram.zip
>
> Time Spent: 6h
> Remaining Estimate: 0h
>
> If an entity defines a collection with a property-ref based key as cacheable, there is a problem loading said collection and putting it into its second level cache region. The issue appears to be due to the incorrect "key" used to locate the owning entity; it tries to use the referenced property value instead of the corresponding id value.
> Workarounds include:
> * Migrating away from property-ref and normalizing the data
> * disabling caching on the collection
> * disabling versioing on the owner
> * disabling versioning on the collection ({{<set ... optimistic-lock="false">}})
--
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
More information about the hibernate-issues
mailing list