You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2010/06/14 19:53:15 UTC

[jira] Closed: (OPENJPA-1641) SybaseDictionary should try both JDBC column names and Sybase specific column names

     [ https://issues.apache.org/jira/browse/OPENJPA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dick closed OPENJPA-1641.
---------------------------------

    Resolution: Fixed

> SybaseDictionary should try both JDBC column names and Sybase specific column names
> -----------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1641
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1641
>             Project: OpenJPA
>          Issue Type: Bug
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>            Priority: Minor
>             Fix For: 1.2.3, 1.3.0, 2.0.1, 2.1.0
>
>         Attachments: OPENJPA-1641.1.2.x.patch.txt, OPENJPA-1641.1.3.x.patch.txt
>
>
> OPENJPA-1326 updated the Sybase dictionary to use Sybase specific column names when inspecting ForiegnKeys and Indexes. While this works with some configurations of Sybase there are some which only use the JDBC names.

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