Bug #22777 CREATE_USER_PRIV doesnt work (?)
Submitted: 28 Sep 2006 11:49 Modified: 28 Oct 2006 11:59
Reporter: Vladimir Kolesnikov Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.22-mac OS:Mac OS X (OS X 10.4.7)
Assigned to: CPU Architecture:Any

[28 Sep 2006 11:49] Vladimir Kolesnikov
Description:
Looks like CREATE_USER_PRIV doesnt work. If this is expected, then i was unable to find anything in docs, so this might be a documentation issue. Or this privilege is not about creating users? (docs are very short about its meaning)

How to repeat:
Let me just paste a cli log

vkolesn-macmini:~/co/common vlad$ /usr/local/mysql/bin/mysql -uroot --host=localhost
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 125 to server version: 5.0.22-max

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> select * from mysql.user where user='root' and host = 'localhost' \G
*************************** 1. row ***************************
                 Host: localhost
                 User: root
             Password: 
          Select_priv: Y
...
 <all privileges = Y>
...
     Create_user_priv: N
             ssl_type: 
           ssl_cipher: 
          x509_issuer: 
         x509_subject: 
        max_questions: 0
          max_updates: 0
      max_connections: 0
 max_user_connections: 0
1 row in set (0.00 sec)

mysql> create user u;
Query OK, 0 rows affected (0.00 sec)
[28 Sep 2006 11:59] Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version of MySQL server, 5.0.24a, and send the reults of

select current_user(), user();

from the same session where you executed CREATE USER.
[9 Oct 2006 10:21] Sergei Golubchik
Try the other way around - all privileges 'N', Create_user_priv='Y'
[28 Oct 2006 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".