Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7521

CONNECT Engine Column names are not retrieved properly when field values are not ANCII characters

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.15, 10.0.16
    • 10.0.18
    • None
    • CentOS, MariaDB 10.0.16, Connect Engine 1.3

    Description

      I am trying to replicate example how to create pivot table like from MariaDB documentation: https://mariadb.com/kb/en/mariadb/documentation/storage-engines/connect/connect-table-types/connect-table-types-pivot-table-type/

      Everything works as fine as explained.
      However, if I replace in source table fields 'Beer' with '啤酒‘ and 'Car' with 'машина‘, I get the following CREATE TABLE statement:

      CREATE TABLE `pivex_cn`
      (
      `who` varchar(135) NOT NULL,
      `week` int(11) NOT NULL,
      `啤酒` decimal(6,2) NOT NULL `FLAG`=1,
      `Food` decimal(6,2) NOT NULL `FLAG`=1,
      `машина` decimal(6,2) NOT NULL `FLAG`=1
      )
      ENGINE=CONNECT DEFAULT CHARSET=utf8 `TABLE_TYPE`='pivot' `TABNAME`='topivot_cn'

      Which then in SELECT * FROM pivex_cn; gives the following error: "Error Code: 1296. Got error 122 'Cannot find matching column' from CONNECT"

      All tables are using utf8 as default. I also tried uft8mb4, the same result

      Bug was discovered first at 10.0.15 MariaDB version, but reproduced in 10.0.16 as well..

      Attachments

        1. source.csv
          0.1 kB
          Evgeny Kosolapov
        2. src.fix
          0.2 kB
          Olivier Bertrand

        Activity

          People

            bertrandop Olivier Bertrand
            eevvkk Evgeny Kosolapov
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.