|
I have been running OSQA for some time, more than one year. My users could login using case insensitive usernames since begining, thats because I'm using case insensitive collation: utf8__unicode__ci. After the last upgrade I did, the case insensitive usernames stop to work, now is necessary to insert the correct cases for the letters. People on Web are used to login without thinking about how their usernames were created. What could be happening, the collation is still the same. How can I enable case insensitive usernames again? Thanks for your help. ps. Sorry about the bad english. |
|
Try executing this query: My guess is that your table collation is utf8_unicode_ci, but in fact utf8_bin is used for the username field. Jordan! Thanks a lot! That was exactly the problem. Now fixed!
(14 Jan, 18:45)
Gallahar
Thanks, that fixed my problem too. And you can execute a similar query on the "name" column for the "forum_tags" table to sort out the similar case insensitivity issue there too
(16 Jan, 13:33)
Joe_Schmoe
|
@Gallahar, all meta.osqa.net postings are required to have a clear, specific question in their title field. Please correct the title of this posting right away. Thanks.
The change in the collation of that field was resulted because you called the "python manage.py syncdb" management command. This action resulted a special callback to be triggered, which is now removed and this should not be an issue anymore. Here's the SVN commit: http://svn.osqa.net/changelog/OSQA/?cs=1220