Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1163543157.1225924484244.JavaMail.jira@brutus>
Date: Wed, 5 Nov 2008 14:34:44 -0800 (PST)
From: "Albert Lee (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Resolved: (OPENJPA-580) Need a better algorithm to find
 DBDictionary classname in DBDictionaryFactory
In-Reply-To: <70839935.1208918363356.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Albert Lee resolved OPENJPA-580.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.3.0

> 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.3.0, 2.0.0
>
>
> 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.