Uploaded image for project: 'MariaDB Connector/node.js'
  1. MariaDB Connector/node.js
  2. CONJS-263

ensure respecting server collation

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 3.2.1
    • other
    • None

    Description

      Connector use utf8mb4 in all exchanges.
      The problem is that current implementation use server truncated collation id in handshake packet. The problem is that when mariadb didn't have lots of collation, a single byte was ok. Since mysql8 and particulary for mariadb since MDEV-27009 that have huge amount of collation, relying on this value is not a good solution.

      New implementation must execute "SET NAMES utf8mb4" by default, ensuring that utf8mb4 will be the charset use in exchange, indicating to server to use correct collation.

      Attachments

        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
          Fix Version/s 3.2.1 [ 29036 ]
          diego dupin Diego Dupin made changes -
          Component/s other [ 14408 ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          diego dupin Diego Dupin added a comment -

          done with https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/df28830994f16d5713b21dfda65165ec1e127e0f

          diego dupin Diego Dupin added a comment - done with https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/df28830994f16d5713b21dfda65165ec1e127e0f

          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.