[
https://issues.apache.org/jira/browse/OPENJPA-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220109#comment-13220109
]
Rick Curtis commented on OPENJPA-2148:
--------------------------------------
> Please fix this issue by changing MaxColumnNameLength in OracleDictionary
> class to 128.
I don't think changing MaxColumnNameLength to 128 is the correct solution. It
sounds like 30 characters is the correct limit, but we need to fix our logic
where we determine the actual length. Somehow we're getting message up when
calculating length + delimiters.
> Issue with MaxColumnNameLength in the OracleDictionary class
> ------------------------------------------------------------
>
> Key: OPENJPA-2148
> URL: https://issues.apache.org/jira/browse/OPENJPA-2148
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.1
> Reporter: aabbcc
> Priority: Blocker
>
> I am using oracle database with OpenJPA.
> The DBDictionary class defines default MaxColumnNameLength as 128.
> But In the OracleDictionary class which extend DBDictionary has
> MaxColumnNameLength as 30. While generating sql query, JPA takes first 28
> characters of the column name and ignores rest of the characters. Also it
> takes start & end quotes, which in total makes it to 30 characters
> Due to this, jpa query fails if there are column in the oracle database with
> more than 28 characters as it finds mismatch in SQL query and actual column
> name.
> Please fix this issue by changing MaxColumnNameLength in OracleDictionary
> class to 128.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
