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

Error message should correctly indicate corrupted foreign keys...

    XMLWordPrintable

    Details

      Description

      When a server has the index supporting a foreign key removed by disabling foreign key checks first, and is later re-started with foreign_key_checks=ON, attempting to read the table produces an error indicating the table does not exist:

      MariaDB [t3]> select count(*) from s3;
      ERROR 1932 (42S02): Table 't3.s3' doesn't exist in engine
      

      and attempting to drop the database produces this error:

      MariaDB [test]> drop database t3;
      ERROR 1010 (HY000): Error dropping database (can't rmdir './t3', errno: 66 "Directory not empty")
      

      Would it be possible for the errors to be more clearly indicative of the corruption in the table structure?

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            juan.vera Juan
            Votes:
            1 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.