Details

    • Technical task
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • 12.1
    • Scripts & Clients
    • None

    Description

      The 'mariadb' client has already support for --catalog

      We should add the --catalog option to all other MariaDB tools using the
      mysql_optionsv(mysql, MARIADB_OPT_CATALOG, catalog);
      call
      (Note that mysql.cc has code to work with client libraries that does not support the
      MARIADB_OPT_CATALOG call. This is there only for developers wanting to know how to
      use catalogs with older client libraries and should not be copied to our other clients).

      Clients to be upgrade:

      • mariadb-admin
      • mariadb-show
      • mariadb-binlog
      • mariadb-dump
      • mariadb-slap
      • mariadb-check
      • mariadb-import
      • mariadb-test
      • mariadb-conv
      • mariadb-plugin
      • mariadb-upgrade
        • Needs to be run for all catalogs
        • We also need to change 'mysql_fix_privilege_tables' to only fix the tables that should exists in the catalog:
          • 'def' has all tables
          • all-other, only the catalog specific tables.

      Attachments

        Activity

          Transition Time In Source Status Execution Times
          Rucha Deodhar made transition -
          Open In Progress
          591d 21h 17m 1
          Rucha Deodhar made transition -
          In Progress In Review
          12s 1
          Rucha Deodhar made transition -
          Stalled In Review
          9d 22h 35m 1
          Oleksandr Byelkin made transition -
          In Review Stalled
          4d 2h 28m 2

          People

            rucha174 Rucha Deodhar
            monty Michael Widenius
            Votes:
            0 Vote for this issue
            Watchers:
            10 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.