openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jody Grassel (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OPENJPA-2432) MySQL dictionarry can't be found from a valid connection
Date Fri, 27 Sep 2013 16:12:03 GMT

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

Jody Grassel updated OPENJPA-2432:
----------------------------------

    Description: The code to check the DB Product Version (the only way to differentiate MariaDB
and MySQL through DBMeta) did not properly handle the fact that MySQL's product version string
did not contain target identifier tokens.  This causes MySQL auto detection to fail.  (was:
Because of a hack to find MariaDB dictionarry, MySQL is never found (cause found then overriden
with null when looking for MariaDB from the version - MySQL rarely (never?) contains its name
in the version))
    
> MySQL dictionarry can't be found from a valid connection
> --------------------------------------------------------
>
>                 Key: OPENJPA-2432
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2432
>             Project: OpenJPA
>          Issue Type: Bug
>            Reporter: Romain Manni-Bucau
>            Assignee: Jody Grassel
>             Fix For: 2.3.0
>
>         Attachments: openjpa-mysql-dict-guess.patch
>
>
> The code to check the DB Product Version (the only way to differentiate MariaDB and MySQL
through DBMeta) did not properly handle the fact that MySQL's product version string did not
contain target identifier tokens.  This causes MySQL auto detection to fail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message