[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-7237) Inline natural-id synchronization doesn't consider reattached objects
Steve Ebersole (JIRA)
noreply at atlassian.com
Mon Apr 23 22:58:48 EDT 2012
[ https://hibernate.onjira.com/browse/HHH-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Ebersole resolved HHH-7237.
---------------------------------
Resolution: Fixed
Fix Version/s: 4.1.3
Assignee: Steve Ebersole
> Inline natural-id synchronization doesn't consider reattached objects
> ---------------------------------------------------------------------
>
> Key: HHH-7237
> URL: https://hibernate.onjira.com/browse/HHH-7237
> Project: Hibernate ORM
> Issue Type: Bug
> Components: core
> Affects Versions: 4.1.2
> Reporter: Guenther Demetz
> Assignee: Steve Ebersole
> Labels: mutable, natural-id
> Fix For: 4.1.3
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Inline natural-id synch process relies on all entity objects in persistence context having it's according natural-id values cached in the NaturalIdResolutionCache.
> While we assured that for the 'persist','update' and 'load from datasource' scenarios, we forgot about reattachements where the object get not load again from datasource, these are: session.update(object) and session.lock(object,LockMode.None).
> The problem rises when detaching objects and then re-attaching them to a new session.
> See pull-requests for solution proposal and according testcases.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list