You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Albert Lee (JIRA)" <ji...@apache.org> on 2008/11/05 20:09:44 UTC
[jira] Assigned: (OPENJPA-580) Need a better algorithm to find
DBDictionary classname in DBDictionaryFactory
[ https://issues.apache.org/jira/browse/OPENJPA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee reassigned OPENJPA-580:
----------------------------------
Assignee: Albert Lee
> Need a better algorithm to find DBDictionary classname in DBDictionaryFactory
> -----------------------------------------------------------------------------
>
> Key: OPENJPA-580
> URL: https://issues.apache.org/jira/browse/OPENJPA-580
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Reporter: Jason Zheng
> Assignee: Albert Lee
> Priority: Minor
>
> When I debug OpenJPA code, I am surprised to find that it creates an instance of AccessDictionary for a sample application which uses Derby.
> The sample application is copied from book "Pro EJB3". The connection URL for the persistence unit is:
> jdbc:derby://localhost:1527/fieldAccess;create=true
> Since it contains 'Access' in the URL value, the OpenJPA code assumes it uses Access database.
> We need a better algorithm to find classname for DBDictionary in DBDictionaryFactory. For example, we can assume the database is Access only if the URL starts with 'jdbc:access'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.