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

ALTER TABLE does not work from client

    XMLWordPrintable

Details

    Description

      Execute from MySQL client (not MTR)

      Welcome to the MariaDB monitor.  Commands end with ; or \g.
      Your MariaDB connection id is 5
      Server version: 10.2.0-MariaDB-debug Source distribution
       
      Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others.
       
      Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
       
      MariaDB [test]> DROP TABLE IF EXISTS t1;
      Query OK, 0 rows affected (0.06 sec)
       
      MariaDB [test]> CREATE TABLE t1 (a INT, b CHAR(8)) ENGINE=InnoDB;
      Query OK, 0 rows affected (0.02 sec)
       
      MariaDB [test]> INSERT INTO t1 (a,b) VALUES (1,'a'),(2,'b'),(3,'c');
      Query OK, 3 rows affected (0.00 sec)
      Records: 3  Duplicates: 0  Warnings: 0
       
      MariaDB [test]> ALTER TABLE t1 MODIFY b CHAR(16);
      ERROR 65535 (HY000): 
      MariaDB [test]> 
      

      It is not the client problem though, the same happens with old client versions. It must be fixed on the server side.

      The problem was introduced by this commit:

      commit d4b3a199acb0ddcdedff441ae664b0a2cf2fe8d2
      Author: Oleksandr Byelkin <sanja@mariadb.com>
      Date:   Sun Jan 17 21:21:39 2016 +0100
       
          MDEV-9117: Client Server capability negotiation for MariaDB specific functionality
          
          New capability flags space.
          Removed old progress flag, added new one.
      

      Attachments

        Activity

          People

            sanja Oleksandr Byelkin
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.