Skip to main content
March 10, 2021
Question

#1267 - illegal mix of collations

  • March 10, 2021
  • 4 replies
  • 0 views

We received the below notification when trying to debug a view, we were not able to export or anything with this error up. The error occured in our UAT environment and this view hasn't been changed in months, all other environments remained unchanged:

I cannot find a reason why this view would fail in only this environment, i have checked the tables and they have also not been changed collation type. Any thoughts much appreciated? 

    4 replies

    March 10, 2021

    Check this article to see if there are problems with the underlying tables: https://interworks.com/blog/bbausili/2010/01/11/mysql-fixing-illegal-mix-collation

    If the tables all turn out with the same collation, maybe try casting or converting hardcoded values, as mentioned in this answer: https://stackoverflow.com/a/37275524

    March 11, 2021

    Unfortunately, the view had been updated from a working environment so i cannot go back and find out the root case in that sense. I have gone through the view's and relevant tables and they don't all have the same collation, they do match the other environments which didn't suffer the same problem. Is there anything else i can do? 

    August 19, 2021

    [mention:d5cd9640b30143808bbe0508ca1407b3:e9ed411860ed4f2ba0265705b8793d05] Thanks for raising , did you get a chance to find out the root cause as we were also facing the same issue, but this time we are facing it in MariaDB rather in MySQL DB.