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

Incorrect information in file: ... #sql-alter ... .frm on ALTER

    XMLWordPrintable

    Details

      Description

      SET @@character_set_server=1;
      DROP DATABASE test;
      CREATE DATABASE test;
      USE test;
      CREATE TABLE t (c1 BLOB);
      ALTER TABLE t ADD c CHAR(30) CHARACTER SET latin1 DEFAULT CONCAT ('ß');
      

      Leads to:

      10.8.0 e222e44d1bfc995870430bb90d8ac97e91f66cb4 (Optimized)

      10.8.0-opt>ALTER TABLE t ADD c CHAR(30) CHARACTER SET latin1 DEFAULT CONCAT ('ß');
      ERROR 1918 (22007): Encountered illegal value 'ß' when converting to big5
      

      And

      10.8.0 e222e44d1bfc995870430bb90d8ac97e91f66cb4 (Optimized)

      2022-01-28 18:58:28 0 [Note] /test/MD190122-mariadb-10.8.0-linux-x86_64-opt/bin/mysqld: ready for connections.
      Version: '10.8.0-MariaDB'  socket: '/test/MD190122-mariadb-10.8.0-linux-x86_64-opt/socket.sock'  port: 37496  MariaDB Server
      2022-01-28 18:58:28 4 [ERROR] mysqld: Incorrect information in file: './test/#sql-alter-1711b9-4.frm'
      

      10.8.0 e222e44d1bfc995870430bb90d8ac97e91f66cb4 (Debug)

      2022-01-28 18:58:17 0 [Note] /test/MD190122-mariadb-10.8.0-linux-x86_64-dbg/bin/mysqld: ready for connections.
      Version: '10.8.0-MariaDB-debug'  socket: '/test/MD190122-mariadb-10.8.0-linux-x86_64-dbg/socket.sock'  port: 30035  MariaDB Server
      2022-01-28 18:58:18 4 [ERROR] mysqld: Incorrect information in file: './test/#sql-alter-16f8fb-4.frm'
      

        Attachments

          Activity

            People

            Assignee:
            bar Alexander Barkov
            Reporter:
            Roel Roel Van de Paar
            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.