MySQL Bugs: #25095: "refresh schemata list" fails for wildcard schema names in "schema privileges"

Bug #25095	"refresh schemata list" fails for wildcard schema names in "schema privileges"
Submitted:	15 Dec 2006 14:36	Modified:	22 Jan 2007 13:00
Reporter:	Yahoo Serious (Silver Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.8	OS:	Windows (Windows 2000 SP4)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
I did not succeed in adding GRANTS (privileges) on a wild card for schema names (see Bug #25094).  So I added them using MySql QueryBrowser.  However, it did not show after a refresh.  I had to restart Administrator.

How to repeat:
- start Administrator
- go to User Administration
- select a certain user U
- go to tab schema privileges

- start QueryBrowser
- change schema privileges: add a privilege with a wild-card schema name for user U

- go back to Administrator
- right click to refresh window (hey, there's a wildcard option!  NB: with typo)
- notice no new wildcard schema (switching tabs, etc. - no effect)
- restart Administrator > User Administration > user U > schema privileges
- notice new wildcard schema 

Suggested fix:
- fix User Administration - schema privileges - refresh schemata list

(small extra request: it would be nice to also have the "refresh" in the View-menu where most applications have it.)

Thank you for a problem report. Please ,try to repeat with a newer version, 1.2.8 (from GUI Tools 5.0r8), and inform about the results.

It still exists in 1.2.8

In QB I use:
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES ON `test1\_%`.* TO 'user1'@'%';

The 'schema name' "test1\_%" is not visible for user "user1" in MA at first, and not after a <refresh>, but it is after a restart of MA.

Thank you for the report.

Verified as described.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html