[OPENJPA-1051] [patch] Mappingtool doesn't check name conflicts if MappingDefaultsImpl is called with multiple columns.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0, 2.0.0-M2
• Fix Version/s: 1.2.0, 2.0.0-M2
• Component/s: jdbc
• Environment: OpenJPA Trunk.
• Assignee: David Ezzio
• Reporter: Ravi Prakash Palacherla
• Created: 28/Apr/09 16:13
• Updated: 21/Sep/16 14:21
• Resolved: 13/May/09 22:57

Description

In OpenJPA implementation, it looks that MappingDefaultsImpl.populateColumns can accept multiple columns
because it has Column[] signature.
If column name is longer than DBDictionary restriction (it's very short in some databases.
For example, oracle max name length is 32), names are truncated.

Because name conflict is detected based on actual Table info,given Column[] data does not get checked.
So, if given Column[] have very long name and truncated name of these Column[] is conflicted,
it could not be detected.