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

emoji is not saving in utf8mb4_myanmar_ci

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.0.19
    • 10.0.20
    • Character Sets
    • None
    • Mac OS X 10.10

    Description

      I am using utf8mb4_myanmar_ci in table. It's working fine for Myanmar Unicode and can sort the correct order. However, it can store emoji text.

      mysql query is like

      INSERT INTO `myanmar`.`sort` (`id`, `my`) VALUES (NULL, 'ပြုံးမောင်မောင် ��');

      But it only store ပြုံးမောင်မောင် and not include emoji icon.

      SHOW TABLE STATUS is showing like that

      Attachments

        Activity

          IF this query:

          SELECT hex(my) from sort;

          distplays:

          F09F9880

          then it means the data has been written into the table correctly.
          Strange. Not sure why you're getting '?' on SELECT.

          bar Alexander Barkov added a comment - IF this query: SELECT hex(my) from sort; distplays: F09F9880 then it means the data has been written into the table correctly. Strange. Not sure why you're getting '?' on SELECT.

          Can you please try to run this:

          SET NAMES utf8mb4;
          SELECT _utf8mb4 X'F09F9880';

          What does it display?

          bar Alexander Barkov added a comment - Can you please try to run this: SET NAMES utf8mb4; SELECT _utf8mb4 X'F09F9880'; What does it display?

          Yes, it's showing F09F9880 . Data has been writing. Let me try on other collection.

          saturngod Htain Lin Shwe added a comment - Yes, it's showing F09F9880 . Data has been writing. Let me try on other collection.

          Oh! it's working fine.

          I clear all the data and start again. It's working fine.

          CREATE TABLE `sample` (
          `id` int(11) NOT NULL AUTO_INCREMENT,
          `my` text COLLATE utf8mb4_myanmar_ci NOT NULL,
          PRIMARY KEY (`id`)
          ) ENGINE=InnoDB AUTO_INCREMENT=18 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_myanmar_ci;

          SET NAMES utf8mb4;
          INSERT INTO `test`.`sample` (
          `my`
          )
          VALUES (
          '��'
          );
          SELECT * FROM sample;

          It's showing correct data.

          I found a problem , it's a problem of php_myadmin and Sequel Pro.

          It's working fine terminal.

          Sorry for wrong report.

          saturngod Htain Lin Shwe added a comment - Oh! it's working fine. I clear all the data and start again. It's working fine. CREATE TABLE `sample` ( `id` int(11) NOT NULL AUTO_INCREMENT, `my` text COLLATE utf8mb4_myanmar_ci NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=18 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_myanmar_ci; SET NAMES utf8mb4; INSERT INTO `test`.`sample` ( `my` ) VALUES ( '��' ); SELECT * FROM sample; It's showing correct data. I found a problem , it's a problem of php_myadmin and Sequel Pro . It's working fine terminal. Sorry for wrong report.

          Perhaps php_myadmin and Sequel Pro have some character set options so this can be properly configured.

          bar Alexander Barkov added a comment - Perhaps php_myadmin and Sequel Pro have some character set options so this can be properly configured.

          People

            bar Alexander Barkov
            saturngod Htain Lin Shwe
            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.