Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 317286

Summary: DB column length not in sync between @Column and @JoinColumn
Product: z_Archived Reporter: Andreas Fischbach <andreas.fischbach>
Component: EclipselinkAssignee: Nobody - feel free to take it <nobody>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P2 CC: adrian.goerler, eclipselink.orm-inbox, guy.pelletier, karenfbutzke, michael.f.obrien, tom.ware
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows Server 2003   
Whiteboard:
Bug Depends on:    
Bug Blocks: 284657    
Attachments:
Description Flags
Proposed changes none

Description Andreas Fischbach CLA 2010-06-18 07:38:51 EDT 
the length specified with @Column for one side of a relation is not recognized by the forwardmapper for the corresponding column on the other side of the relation. @Joincolumn has no length attribute and should take the one from the other side of the relation to make sure join columns have the same type and length.
Problem arises if a dbplatform creates different datatypes depending on the length of a field
Comment 1 Tom Ware CLA 2010-08-09 14:03:12 EDT 
Setting target and priority.  See the following page for details of the meanings of these fields:

http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines
Comment 2 Guy Pelletier CLA 2010-09-03 13:26:25 EDT 
Created attachment 178178 [details]
Proposed changes
Comment 3 Guy Pelletier CLA 2010-09-03 14:54:00 EDT 
Changes were submitted

Reviewed by: Chris Delahunt

New test (testJoinColumnForeignKeyFieldLength) added to AdvancedJPAJunitTest
Comment 4 Guy Pelletier CLA 2010-09-10 08:37:50 EDT 
*** Bug 241704 has been marked as a duplicate of this bug. ***
Comment 5 Eclipse Webmaster CLA 2022-06-09 10:18:53 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink