Domain and nameserver searches treat similar unicode chars (á ~ a) as the same

[TheRedTrainer]

If a client search a domain or a nameserver by unicode name that includes a char with a similar unicode value (for example á ~ a) the db return all the coincidences for the char. If a client want to retrieve data from domain "exámple.com", the query returns all the coincidences that matches similar unicode chars (example.com, éxample.com, exámple.com, examplé.com, éxámplé.com), beside the fact that the ldh_name for these domains are different because áa, ée have differente unicode values.

The query should search for the exact unicode char, at leats in domain unicode name search.

[pcarana]

Debugging the issue, this seems to be at DB level. The implementation honours what the server sent (A-Label or U-Label), so that's good news.

The problem was reproduced at a MySQL 5.6 DB, and is behavior of the collation. An example can be seen here: 10.1.8.6 Examples of the Effect of Collation. Quoting some content of the link (just to have an idea):

This is not a bug but rather a consequence of the sorting properties...

More information at 10.1.10.1 Unicode Character Sets.

So, the database is the one with the problem, the comparisson of special characters (even when the DB supports UTF-8) doesn't works as we should normally expect, it isn't so restrictive to treat "á" as a different char than "a"; too bad for us, but that's how things are =|

[TheRedTrainer]

Verified. This issue is related to DB management system, so it's not possible to validate it in the server.

[pcarana]

Closing, fixed in Red Dog v1.2