There is something disturbing about this behavior.
I can only think of two circumstances when SELECTs can run unrestained like this:
SITUATION #1: skip-grant-tables in /etc/my.cnf
Please check that /etc/my.cnf does not have this:
[mysqld]
skip-grant-tables
If it does, remove the skip-grant-tables
line and restart mysql right away.
SITUATION #2: skip-grant-tables from command line
It is possible to start mysql with the skip-grant-tables
option without touching my.cnf. In Linux OS, please run this:
$ service mysql start --skip-grant-tables
From the Linux command line, to find out if skip-grant-tables
is activated, pleasd run this:
$ mysqld --help --verbose | grep -C 3 "skip-grants"
You will see lines that look something like this:
secure-file-priv (No default value)
server-id 106451130
show-slave-auth-info FALSE
skip-grant-tables FALSE
skip-name-resolve TRUE
skip-networking FALSE
skip-show-database FALSE
If skip-grant-tables
is TRUE, just restart mysql as normal. It should then disappear.
Give it a Try !!!
CAVEAT : If this is a MySQL/Windows issue, please inspect my.ini
Also, there is no global variable to change this feature. This option applies to the startup of mysql only.
UPDATE 2011-09-09 12:56 EDT
Try using this SQL Command once you login:
SELECT USER(),CURRENT_USER();
These functions report the way you authenticate
USER() reports how you attempted to authenticate in MySQL
CURRENT_USER() reports how you were allowed to authenticate in MySQL
Please update your question with these findings !!!