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

implement SHOW CREATE ROLE

    XMLWordPrintable

Details

    Description

      SHOW CREATE ROLE doesn't work.

      See here:

      MariaDB [(none)]> CREATE ROLE 'admin_role';
      		 
      Query OK, 0 rows affected (0.002 sec)
      		 
       
      		 
      MariaDB [(none)]> CREATE ROLE 'user_role'  WITH ADMIN 'admin_role';
      		 
      Query OK, 0 rows affected (0.004 sec)
      		 
       
      		 
      MariaDB [(none)]> SHOW CREATE ROLE 'user_role';
      		 
      ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'ROLE 'user_role'' at line 1

      Since you can create a role with its own WITH ADMIN clause, this statement should be implemented, so that all role attributes can be easily printed.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22312 Bad error message for SET DEFAULT ROLE when user account is not granted the role

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22313 SHOW GRANTS does not prints a user's default role

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-23630 mysqldump to logically dump system tables

          • Major - Major loss of function.
          • Closed

          Activity

            People

              ralf.gebhardt Ralf Gebhardt
              GeoffMontee Geoff Montee (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              8 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.