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

SHOW CREATE USER generates invalid SQL

    XMLWordPrintable

Details

    Description

      MariaDB [(none)]> show create user;
      +---------------------------------------------------------------------------------------------------+
      | CREATE USER for dan@localhost                                                                     |
      +---------------------------------------------------------------------------------------------------+
      | CREATE USER `dan`@`localhost` IDENTIFIED VIA mysql_native_password USING 'invalid' OR unix_socket |
      +---------------------------------------------------------------------------------------------------+
      1 row in set (0.000 sec)
       
      MariaDB [(none)]>  CREATE USER `dan2`@`localhost` IDENTIFIED VIA mysql_native_password USING 'invalid' OR unix_socket
          -> ;
      ERROR 1372 (HY000): Password hash should be a 41-digit hexadecimal number
      

      Is "invalid" something that should be literally accepted for compatibility?

      To not do so means programs and humans that use SHOW CREATE USER output needs to parse out this text and remove it.

      Attachments

        Issue Links

          Activity

            People

              danblack Daniel Black
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 25m
                  25m

                  Git Integration

                    Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.