Uploaded image for project: 'MariaDB Connector/J'
  1. MariaDB Connector/J
  2. CONJ-321

Handle 10.2 server "forced" version

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 1.5.0-RC
    • Other
    • None

    Description

      since 10.2, server version can be forced.
      driver actually use this version, checking string "MariaDB" to identify if server is Mysql or Mariadb.
      This permit to handle an error in OKPacket that MySQL solved only in 5.7.5 (mariadb solved in in first 5.5 version).

      This identification need to be removed

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-7780 Support for faking server version

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            diego dupin Diego Dupin created issue -
            diego dupin Diego Dupin made changes -
            Field Original Value New Value
            diego dupin Diego Dupin made changes -
            Fix Version/s 1.5.0 [ 19607 ]
            diego dupin Diego Dupin made changes -
            Summary Handle 10.2 server "force" version Handle 10.2 server "forced" version
            diego dupin Diego Dupin made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 76343 ] MariaDB v4 [ 134889 ]

            People

              diego dupin Diego Dupin
              diego dupin Diego Dupin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.