Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346289 - PK should be populated when creating new originals for merge
Summary: PK should be populated when creating new originals for merge
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-18 11:38 EDT by Gordon Yorke CLA
Modified: 2022-06-09 10:27 EDT (History)
1 user (show)

See Also:

Attachments
Patch (1.52 KB, patch)
2011-05-18 11:40 EDT, Gordon Yorke CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon Yorke CLA 2011-05-18 11:38:25 EDT 
When creating a new original for merging of related existing objects the new Entity should have the PK populated as it may be needed later to determine identity of that related Entity.
Comment 1 Gordon Yorke CLA 2011-05-18 11:40:46 EDT 
Created attachment 195993 [details]
Patch

Change getTargetVersionOfSourceObject on MergeManager to populate the PK if it is not populated by the copy policy
Comment 2 Gordon Yorke CLA 2011-05-20 08:55:37 EDT 
Simple patch checked in
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:27:02 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink