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

Always check table options in ALTER TABLE…ALGORITHM=INPLACE

    Details

      Description

      The test encryption.innodb-spatial-index creates a table with ENCRYPTED=YES, and then expects an ADD SPATIAL INDEX, ALGORITHM=COPY operation to fail. However, an operation with FORCE, ALGORITHM=COPY is just fine (in both 10.1 and 10.2):

      --source include/have_innodb.inc
      --source include/have_file_key_management_plugin.inc
       
      CREATE TABLE t1 (pk INT PRIMARY KEY AUTO_INCREMENT,
      c VARCHAR(256), coordinate POINT NOT NULL) ENCRYPTED=YES ENGINE=INNODB;
      ALTER TABLE t1 FORCE, ALGORITHM=COPY;
      ALTER TABLE t1 FORCE, ALGORITHM=INPLACE;
      DROP TABLE t1;
      

      In my opinion, ALTER TABLE...ALGORITHM=COPY must always succeed, and it must always preserve those table attributes that were not specified in the ALTER.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                marko Marko Mäkelä
                Reporter:
                marko Marko Mäkelä
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: