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

["Ravi P Palacherla (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OPENJPA-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705590#action_12705590 ] 

Ravi P Palacherla commented on OPENJPA-1051:
--------------------------------------------

Can someone please commit the patch.

> [patch] Mappingtool doesn't check name conflicts if MappingDefaultsImpl is called with multiple columns.
> --------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1051
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1051
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.0.0, 2.0.0
>         Environment: OpenJPA Trunk.
>            Reporter: Ravi P Palacherla
>         Attachments: OPENJPA-1051_Trunk.patch
>
>
>  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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.