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

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikeytown2’s picture

Title: Use utf8_bin instead of utf_unicode_ci for the varchar database columns » Use utf8_bin instead of utf8_unicode_ci for the varchar database columns

  • mikeytown2 committed 53e5c28 on 7.x-2.x
    Issue #2418935 by mikeytown2: Use utf8_bin instead of utf8_unicode_ci...
mikeytown2’s picture

First part done; getting it to work on new installs of advagg. Next step is to write the hook update for current installs.

mikeytown2’s picture

Status: Active » Fixed
FileSize
2.74 KB

  • mikeytown2 committed b99dbcb on 7.x-2.x
    Issue #2418935 by mikeytown2: Use utf8_bin instead of utf8_unicode_ci...
joelpittet’s picture

This 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.

mikeytown2’s picture

Backport 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.

joelpittet’s picture

Ok, 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.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.