Comment 2 for bug 1252327

The "workaround" listed in the original description actually requests the removal of a user at the host 127%2e0%2e0%2e1, which is not a valid host address. The behavior of the current service requires twice percent encoding periods in names, which is directly opposed to RFC 3986 §2.3.

In addition, the documentation does not specify what the allowed set of code points is for a username or database name. It does however specify that the database instance is MySQL, so a developer could easily and reasonably infer that `%`, `2`, and `e` are all valid characters in a name. The current implementation would take the valid name `MyData%2e` and turn it into `MyData.`.