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

MariaDB-10.2.30 grant command issue

    XMLWordPrintable

    Details

      Description

      OS : CentOS7 x86_64
      mariadb-10.2.30-linux-glibc_214-x86_64

      MariaDB [(none)]> show grants for foo;
      +----------------------------------------------------------------------------------------------------+
      | Grants for foo@%                                                                                   |
      +----------------------------------------------------------------------------------------------------+
      | GRANT USAGE ON *.* TO 'foo'@'%' IDENTIFIED BY PASSWORD '*F3A2A51A9B0F2BE2468926B4132313728C250DBF' |
      | GRANT ALL PRIVILEGES ON `db1`.* TO 'foo'@'%'                                                       |
      | GRANT ALL PRIVILEGES ON `db2`.* TO 'foo'@'%'                                                       |
      +----------------------------------------------------------------------------------------------------+
      3 rows in set (0.00 sec)
      

      in current settings

      ------------------------------------------------------------
      MariaDB [(none)]> grant SELECT ON db3.* to foo@'%';
      Query OK, 0 rows affected (0.00 sec)
      ------------------------------------------------------------
      

      after executing the command!
      update command denied to user for db2 in application!

      If there are many transactions
      Are there any bugs with that version?
      Reproduction is not possible.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            Na YunHo
            Votes:
            0 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.