openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Catalina Wei (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OPENJPA-617) Use of hardcoded DB platform strings should be avoided
Date Thu, 29 May 2008 04:00:44 GMT

     [ 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.


Mime
View raw message