Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-31542 Add multi-tenancy catalogs to MariaDB
  3. MDEV-33695

Catalogs: DROP CATALOG should have a FORCE option

Details

    • Technical task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • None
    • N/A
    • catalogs
    • None

    Description

      DROP CATALOG will not drop a catalog any databases apart from information_schema exist. This is likely a good thing to stop accidental usage. But, an override should exist. I recommend adding a FORCE keyword for this. But worse case DROP CATALOG shouldn't care if databases still exist.

      Attachments

        Issue Links

          is duplicated by

          Technical task - A technical task. MDEV-33694 create and drop catalogs inside MariaDB Server

          • Major - Major loss of function.
          • Closed

          Activity

            monty Michael Widenius added a comment - - edited

            This is now implemented as part of MDEV-33694
            DROP CATALOG name now drops everything in the catalog

            monty Michael Widenius added a comment - - edited This is now implemented as part of MDEV-33694 DROP CATALOG name now drops everything in the catalog

            People

              monty Michael Widenius
              TheLinuxJedi Andrew Hutchings (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.