You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Catalina Wei (JIRA)" <ji...@apache.org> on 2008/05/29 06:00:44 UTC

[jira] Resolved: (OPENJPA-617) Use of hardcoded DB platform strings should be avoided

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

Catalina Wei resolved OPENJPA-617.
----------------------------------

    Resolution: Fixed

1. The hard coded "Oracle" String has been removed.
2. Not all jdbc driver have  the connection  APIs available.
   Tthe trace info for the  initial connection propertities are only available to JDBC 3 drivers.
   For this reaon, this particular message trace is removed from DataSourceFactory,
   but placed in DBDictionary.
   Because of this move, some message text has be relocated into org.apache.openjpa.jdbc.sql package.

> Use of hardcoded DB platform strings should be avoided
> ------------------------------------------------------
>
>                 Key: OPENJPA-617
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-617
>             Project: OpenJPA
>          Issue Type: Bug
>            Reporter: Catalina Wei
>            Assignee: Catalina Wei
>
> This is a bad practice in the code that I recently put in.
> Hard-coded "Oracle" string should be avoided.

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