Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357407 - composite foreign keys are defaulted wrong in OneToOne, ManyToOne
Summary: composite foreign keys are defaulted wrong in OneToOne, ManyToOne
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal with 3 votes (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-12 14:59 EDT by James Sutherland CLA
Modified: 2022-06-09 10:32 EDT (History)
2 users (show)

See Also:

Attachments
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 James Sutherland CLA 2011-09-12 14:59:22 EDT 
If you have a OneToOne say manager to Employee with Id ID

 then we correctly default the foreign key to MANAGER_ID,

but if you have a composite Id, ID, ID2, then we default wrong,

  ID, ID2

we omit the prefix, which will not work
Comment 1 Tom Ware CLA 2011-10-13 13:26:48 EDT 
Setting target and priority.  See the following page for the meanings of these fields:

http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines

Community: Please vote for this bug if it is important to you.  Votes are one of the main criteria we use to determine which bugs to fix next.
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:32:31 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink