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

The Cyrillic string is not truncated by the number of characters when using the Connect Engine table

    XMLWordPrintable

    Details

      Description

      Good afternoon, I previously used version 10.5.8 together with Connect Engine to display third-party information from other databases, there were no problems
      That is, I created a table pointing to a table from the MSSQL database and the information was displayed successfully

      After that, I installed MariaDB 10.6.7 separately and I did the same thing and noticed one feature that now lines containing Cyrillic do not fit into the allotted number of characters.

      In other words, I have a string in MSSQL: ИВАНОВА

      When I created in MariaDB table with row VARCHAR(1) and get next:
      10.5.8 = И
      10.6.7 = ?

      Change to VARCHAR(2)
      10.5.8 = ИВ
      10.6.7 = И

      Change to VARCHAR(3)
      10.5.8 = ИВА
      10.6.7 = ИВ

      Change to VARCHAR(4)
      10.5.8 = ИВАН
      10.6.7 = ИВ?

      Change to VARCHAR(5)
      10.5.8 = ИВАНО
      10.6.7 = ИВА

      If row without cyrillic, only latin or numbers for example IVANOVA
      All excellent:

      10.5.8 = I
      10.6.7 = I

      Change to VARCHAR(2)
      10.5.8 = IV
      10.6.7 = IV

      Change to VARCHAR(3)
      10.5.8 = IVA
      10.6.7 = IVA

      It seems that he began to somehow divide the multibyte Cyrillic and other special characters

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              monty Michael Widenius
              Reporter:
              long.skinny.boy long.skinny.boy
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration

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