openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Ezzio (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-580) Need a better algorithm to find DBDictionary classname in DBDictionaryFactory
Date Mon, 15 Jun 2009 17:28:07 GMT

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

David Ezzio updated OPENJPA-580:
--------------------------------

    Fix Version/s: 1.1.1

Merged changes on DBDictionaryFactory and TestDictionaryFactory to Branch 1.1.x at rev 784867.
 

> 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
>             Fix For: 1.1.1, 1.3.0, 2.0.0-M2
>
>
> 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.


Mime
View raw message