openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milosz Tylenda (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OPENJPA-933) Database version detection in MySQLDictionary is not reliable
Date Sat, 18 Apr 2009 13:01:16 GMT

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

Milosz Tylenda resolved OPENJPA-933.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.3.0

A patch applied to trunk and 1.3.x branch.

Changes:
- Corrected version parsing for non-JDBC 3 drivers
- Version numbers are got from JDBC 3 methods if available
- Removed driver version parsing, now uses metaData.getDriverMajorVersion() which is a pre-JDBC
3 method


> Database version detection in MySQLDictionary is not reliable
> -------------------------------------------------------------
>
>                 Key: OPENJPA-933
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-933
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc, sql
>    Affects Versions: 1.2.0, 1.3.0, 2.0.0
>         Environment: MySQL 5.1.30, Linux
>            Reporter: Milosz Tylenda
>            Assignee: Milosz Tylenda
>            Priority: Minor
>             Fix For: 1.3.0, 2.0.0
>
>
> The database version detection code assumes the version string always looks like "4.1.3-nt"
whereas currently a MySQL on Linux reports itself as "5.1.30". This causes an exception catch
and a fallback to default values (in particular supportsXMLColumn stays false). Also, the
code could take advantage of JDBC 3 methods that return version numbers.
> I will provide a patch.

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