Closed marquisite closed 10 years ago
Ah, I didn't know it was doing that. This is probably the best solution. I doubt changing to utf8_general would break anything for most people, but usernames are meant to be unique and case sensitive, and so an SQL comparison would want to be case sensitive. Also I think the general collations ignore accents on characters, which could be a bad issue.
This modification was originally posted to Google Groups by Ingrid but I think it would be of benefit to AJAX-Chat (it is so simple).
There are some alternatives to this method, like changing the collation of the userName field in ajaxchat_online from "utf_bin" to "utf8_general_ci".
With multiple language translations, I'm not sure which of these methods would be best.