Bug #27488 User Creation Error
Submitted: 28 Mar 2007 7:36 Modified: 30 May 2007 7:23
Reporter: Paul Rudge Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Administrator Severity:S1 (Critical)
Version:Falcon 5.2 OS:Windows (Win 2K)
Assigned to: CPU Architecture:Any
Tags: management, user

[28 Mar 2007 7:36] Paul Rudge
Description:
After creating a second user and then adjusting the resources for ROOT (which I personally think is a BAD idea) The system reports correctly in that the DB access error after questions exceed my input limit set to 1000 in 1hr.

At which point MYSQL thinks that the user profiles are now corrupt and reports invalid configuration - user may be deleted, try refresh.

Although it has saved the changes to the user managment on screen - IT HAS NOT!

root and any other user management changes are NOW invalid, resources, schemas, etc.......

How to repeat:
CANNOT - User management profiles corrupt. I can create new user and clone the original but cannot modify its security or attach via Connector(ODBC)

Only one profile is now active and I CANNOT modify it in any way!!

Suggested fix:
LOCK the ROOT and DO NOT allow any security changes - root should always be GOD status and CANNOT be demoted - diable its name maybe - but only if another user haas GOD status
[28 Mar 2007 15:40] Valeriy Kravchuk
Thank you for a problem report. Please, inform about the exact MySQL Administrator version used (1.x.y). Exact steps to repeat this problem based on fresh installation of MySQL server will be also useful.
[28 Apr 2007 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".
[30 Apr 2007 7:23] Valeriy Kravchuk
Feedback is still needed.
[30 May 2007 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".