MySQL Bugs: #26691: Schemata list under Schema Privileges for a new user shows escape character (\)

Bug #26691	Schemata list under Schema Privileges for a new user shows escape character (\)
Submitted:	27 Feb 2007 19:31	Modified:	30 May 2007 12:13
Reporter:	Marc Hodgins (Candidate Quality Contributor)	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.9	OS:	Windows (Windows XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Schemata list on Schema Privileges tab when creating a new user account shows schemas like this:

information\_schema
another\_schema
mysql

etc

Looks like a misplaced string escape character.

How to repeat:
Click User Administration
Click Add new user
Click Schema Privileges tab

Thank you for a bug report. Verified just as described.

I have a database listed TWICE under User Administration, Schema Priveleges tab.

the database is called BR08_contact. There is only one such db in the data folder. The Schemata listing shows:

BR08\_contact
BR08_contact

What is especially disturbing is that changing a user's rights in one of these schemas does not change it in the other. Apparently, the schema name with the backslash is a ghost in this instance, changes to it do net affect a user's rights to the single actual database.

Same here... Most disturbing is that a single db may be listed twice in the list... Once escaped, and another non-escaped:

db_1

-and-

db\_1

Assigning rights to either of these is unpredictable (some users have entries for one, or the other, or both??

Both entries are valid user rights pattern. "db_1" means all schemas starting with "db", one arbitrary character after that and ending with "1". "db\_1" means exactly the the schema db_1. These entries can only appear if you have entered them as schema rights aren't given automatically.

If you are sure that you have only entered one of the two forms then please provide me with exact steps how to reproduce it.

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".