Closed
Bug 1221061
Opened 9 years ago
Closed 8 years ago
Move to utf8_bin for tag columns
Categories
(developer.mozilla.org Graveyard :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jezdez, Assigned: jezdez)
Details
(Keywords: in-triage, Whiteboard: [specification][type:change])
What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== We're currently using a custom MySQL collation to support case insensitivity for queries against the tag table. Since taggit supports a new feature that makes it case insensitive and we want to get rid of the custom collation for operational reasons (moving to Amazon's RDS) we should look into this. What problems would this solve? =============================== This would remove a big blocker for moving to AWS. Who would use this? =================== n/a What would users see? ===================== n/a What would users do? What would happen as a result? =================================================== n/a Is there anything else we should know? ======================================
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jezdez
Assignee | ||
Comment 1•8 years ago
|
||
Gonna call that invalid now that we work on going over to Postgres in bug 1159930.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•