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

Check when doing ALTER TABLE table_name sequence=1 that table can be a sequence

    XMLWordPrintable

Details

    Description

      When doing an ALTER TABLE table_name sequence=1 we should give an error if:

      • That table definition does not match what is required by sequences.
      • This should already be the case
      • The table has 1 row
      • The content matches an allowed sequence state

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35866 mariadb-check does not return warning for incorrect sequence with engine InnoDB

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-36856 Remove the error codes added to 10.11 by the MDEV-36032 patch

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-22491 Support mariadb-check and CHECK TABLE with SEQUENCE

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-36038 ALTER TABLE…SEQUENCE does not work correctly with InnoDB

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

          Activity

            People

              ycp Yuchen Pei
              monty Michael Widenius
              Votes:
              0 Vote for this issue
              Watchers:
              7 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.