Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329521 - Foreign Key Constraints are not created because the names are not unique. May effect other Constraint or Table names as well!
Summary: Foreign Key Constraints are not created because the names are not unique. May...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-05 05:23 EDT by Michael Niedermaier CLA
Modified: 2022-06-09 10:34 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 Michael Niedermaier CLA 2010-11-05 05:23:21 EDT 
Build Identifier: Eclipse 20100617-1415 (EclipseLink v2.1.0)

Problem is, that the Names are shortend (to DB-Max-Signs) by removing underscores, numbers and then vocals:
1. This may lead to duplicate names of foreign keys 
2. If Name (maybe this also happens to table names) is like "A74328......." and it is too long, the name is shortended by removing the leading vocal "A". In e.g. Oracle, names with leading numbers can only be used if the the name is set in between quotation marks, what is not done by EclipseLink.

Reproducible: Always
Comment 1 Tom Ware CLA 2010-11-18 08:25:13 EST 
Setting target and priority.  See the following page for the meanings of these fields:

http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:34:28 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink