Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336754 - constraint issues with mapped key mappings
Summary: constraint issues with mapped key mappings
Status: NEW
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: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-09 14:59 EST by James Sutherland CLA
Modified: 2022-06-09 10:08 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Sutherland CLA 2011-02-09 14:59:16 EST
If a collection mapping uses a mapped key using a 1-1 or aggregate, it needs to cascade the pre/postInsert/Update/Delete mapping events into the mapping.  Although CollectionMapping seems to do this, most subclasses override these methods and don't seem to do it.

This could lead to constraint issues, or missed writes/delete for aggregate relationships.

Also the new code for handling deletion cycles does not account for mapped keys.  Not sure if our constraint dependencies do either.
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:08:03 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink