Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
In theory this should speed up all advagg queries due to MySQL not needing to apply Unicode normalization to the query conditions.
http://stackoverflow.com/questions/10929836/utf8-bin-vs-utf-unicode-ci
Comment | File | Size | Author |
---|---|---|---|
#4 | advagg-2418935-4-use-utf8_bin.patch | 2.74 KB | mikeytown2 |
#3 | advagg-2418935-utf8_bin-instead-of-utf8_unicode_ci.patch | 5.05 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedComment #3
mikeytown2 CreditAttribution: mikeytown2 commentedFirst part done; getting it to work on new installs of advagg. Next step is to write the hook update for current installs.
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedComment #6
joelpittetThis change is quite drastic, are you sure it's the right way to go? A bit worried rolling this change out mostly because the field changes.
Comment #7
mikeytown2 CreditAttribution: mikeytown2 commentedBackport from D8 #2352207: Database cache backend does not treat cid as case sensitive.
Should give a small speed bump to all queries as well.
Targets MySQL only due to Postgres being case sensitive where as MySQL is case insensitive.
Comment #8
joelpittetOk, I'll trust you on this one;) I've not used different collations as binary before so it looked worrisome thanks or the D8 reference.