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

Document that SHOW CREATE TABLE on InnoDB tables only shows ROW_FORMAT when explicitly set

    XMLWordPrintable

Details

    Description

      Not sure whether this should be bug or task, but ...

      When creating an InnoDB table with explicit ROW_FORMAT the ROW_FORMAT is shown on SHOW CREATE TABLE, when using the implicit default on the other hand this is not shown in SHOW CREATE output.

      Now when using SHOW CREATE output for creating the table on a new server for doing an ALTER...IMPORT there, if ROW_FORMAT was not explicitly set, and the default setting differs between source and target server, the IMPORT will fail.

      This can of course be worked around by adding the correct ROW_FORMAT manually, but it is an odd step to take ...

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-11658 Simpler, faster IMPORT of InnoDB tables

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. MDEV-18762 Support easy restore of partial backup

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15049 Importing InnoDB table from 10.1 to 10.2 causes Schema mismatch (Expected FSP_SPACE_FLAGS=0x21, .ibd file contains 0x0

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16851 On schema mismatch in IMPORT TABLESPACE, display ROW_FORMAT in clear text

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-20932 Create a way to reliably create a table for IMPORT

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-20974 Don't require .cfg files to import InnoDB tablespaces

          • Major - Major loss of function.
          • Closed

          Activity

            People

              GeoffMontee Geoff Montee (Inactive)
              hholzgra Hartmut Holzgraefe
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.