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

Small correction for error shown when using invalid ENCRYPTION_KEY_ID

    XMLWordPrintable

Details

    Description

      12.0.0-opt>ALTER TABLE t1 ENCRYPTION_KEY_ID=2;
      Query OK, 0 rows affected (0.007 sec)
      Records: 0  Duplicates: 0  Warnings: 0
       
      12.0.0-opt>ALTER TABLE t1 ENCRYPTION_KEY_ID=3;
      ERROR 1478 (HY000): Table storage engine 'InnoDB' does not support the create option 'ENCRYPTION_KEY_ID'
      

      The reason the error is shown is that the specified encryption_key_id did not exist in the keyfile used.

      The message is incorrect: InnoDB does support the option ENCRYPTION_KEY_ID, as per the example directly above it.

      Instead, we could use something like "ENCRYPTION_KEY_ID 3 does not exist in the keyfile".

      Attachments

        Activity

          People

            marko Marko Mäkelä
            Roel Roel Van de Paar
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.