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

After alter table the table ends up in corrupted state

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 11.8.5, 11.8.8
    • None
    • None
    • MacOS + Docker mariadb:11.8.8

    Description

      Run the following SQL:

      CREATE TABLE `integrationSystems` (
        `id` int(11) NOT NULL AUTO_INCREMENT,
        `name` varchar(60) NOT NULL,
        PRIMARY KEY (`id`),
        UNIQUE KEY `uniq_integrationsSystems_name` (`name`),
        KEY `idx_integrationsSystems_id` (`id`)
      ) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE = utf8mb4_unicode_ci;
       
      ALTER TABLE integrationSystems MODIFY id INT NOT NULL;
      DROP INDEX `primary` ON integrationSystems;
      DROP INDEX idx_integrationsSystems_id ON integrationSystems;
      DROP INDEX uniq_integrationsSystems_name ON integrationSystems;
      

      You should get "Table 'mydb.#sql-backup-1-6' doesn't exist".

      Note that this code is auto generated by symfony doctrine, so in theory it should be okay from logic and syntax perspective. Apparently it still damages the table. In a modified version I even get "General error: 1033 Incorrect information".

      I am curious if there is any workaround for this or why this fails? Currently it is blocking the migration of my project.

      Attachments

        Activity

          People

            shipjain Shipra Jain
            inf3rno Lajos Jánszky
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.