OpenJPA
  1. OpenJPA
  2. OPENJPA-933

Database version detection in MySQLDictionary is not reliable

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.2.0, 1.3.0, 2.0.0-M2
    • Fix Version/s: 1.3.0, 2.0.0-M2
    • Component/s: jdbc, sql
    • Labels:
      None
    • Environment:
      MySQL 5.1.30, Linux

      Description

      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.

        Activity

        Hide
        Milosz Tylenda added a comment -

        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
        Show
        Milosz Tylenda added a comment - 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

          People

          • Assignee:
            Milosz Tylenda
            Reporter:
            Milosz Tylenda
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development