#2855 (ok 3.1.4) Privileges SQL Error with MySQL 5.1.33
Hi, when I view a database and click "Privileges" I get the following error
"SQL query: DocumentationEdit
(SELECT `User`, `Host`, `Select_priv`, `Insert_priv`, `Update_priv`, `Delete_priv`, `Create_priv`, `Drop_priv`, `Grant_priv`, `Index_priv`, `Alter_priv`, `References_priv`, `Create_tmp_table_priv`, `Lock_tables_priv`, `Create_view_priv`, `Show_view_priv`, `Create_routine_priv`, `Alter_routine_priv`, `Execute_priv`, `Event_priv`, `Trigger_priv`, `Db` FROM `mysql`.`db` WHERE 'mysql' LIKE `Db` AND NOT (`Select_priv` = 'N' AND `Insert_priv` = 'N' AND `Update_priv` = 'N' AND `Delete_priv` = 'N' AND `Create_priv` = 'N' AND `Drop_priv` = 'N' AND `Grant_priv` = 'N' AND `References_priv` = 'N' AND `Create_tmp_table_priv` = 'N' AND `Lock_tables_priv` = 'N' AND `Create_view_priv` = 'N' AND `Show_view_priv` = 'N' AND `Create_routine_priv` = 'N' AND `Alter_routine_priv` = 'N' AND `Execute_priv` = 'N' AND `Event_priv` = 'N' AND `Trigger_priv` = 'N')) UNION (SELECT `User`, `Host`, `Select_priv`, `Insert_priv`, `Update_priv`, `Delete_priv`, `Create_priv`, `Drop_priv`, `Grant_priv`, `Index_priv`, `Alte[...]
MySQL said: Documentation
#1054 - Unknown column 'Event_priv' in 'field list' "
I am using phpmyadmin 3.1.3.1 mysql 5.1.33 and php 5.2.9
If I click "Privileges" on the server screen it works fine.
Regards
Rowan
Note: I just tested this on MySQL 5.0.77 and it works fine so it seems to be a MySQL 5.1 problem.
I am using MySQL 5.1.33 and phpMyAdmin 3.1.3.1 on an Apache 2.2.11 with PHP 5.2.8 (+ Suhosin Patch) and it works for me without an error.
Maybe you updated MySQL from version 5.0 or older without migrating the "mysql" table to the newest version with the "mysql_upgrade" command. The "event schedule" was introduced in MySQL 5.1 and this missing column "Event_priv" should be added like the new table "event" and some other changes in the database "mysql" while running "mysql_upgrade".
Best regards
Thanks for that you're right I forgot to run mysql_upgrade, sorry for the false report.
Ok but there is some logic in phpMyAdmin that is supposed to warn you about this, I'll check about it.
FAQ 1.41 added.