Bug #6869

normalization.csv is now case sensitive

Added by Sarah Romkey almost 8 years ago. Updated about 5 years ago.

Status:NewStart date:06/19/2014
Priority:LowDue date:
Assignee:-% Done:


Target version:-
Google Code Legacy ID: Pull Request:
Sponsored:No Requires documentation:


After a patch to be applied to 1.2, the normalization.csv will then be case sensitive. From Holly's email:

"Manual normalization with normalization.csv used to support differing cases - if the file was named Image.PNG on disk, but called image.png in normalization.csv it would still match. However, we changed the db field that stores locations to be a longblob because unicode and <blah blah technical explanation Django and MySQL unhappy> it doesn't match case insensitive anymore.

This would probably be a pain to fix, since Django and MySQL have different ideas of whether or not that field is case sensitive."

We will document how this procedure now works, however, it would be desirable to return to the case insensitive behavior.


#1 Updated by Nick Wilkinson about 5 years ago

  • Assignee deleted (Holly Becker)

Also available in: Atom PDF