Views error
Not sure wether this is the best place to post this, but I have what seems to be a problem. Since I cannot see any problems in functionality I am not too worried. I get this error on some of my views, whilst in admin mode only, all else seems to be workig!
* user warning: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' query: SELECT s.uid, v.updated FROM views_object_cache v INNER JOIN sessions s ON v.sid = s.sid WHERE s.sid != '9061a7e5056174f627a75855e55d7b2b' and v.name = 'NodNamNum' and v.obj = 'view' ORDER BY v.updated ASC in /home/mdg/public_html/modules/views/views_ui.module on line 242.
* user warning: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' query: SELECT s.uid, v.updated FROM views_object_cache v INNER JOIN sessions s ON v.sid = s.sid WHERE s.sid != '9061a7e5056174f627a75855e55d7b2b' and v.name = 'NodNamNum' and v.obj = 'view' ORDER BY v.updated ASC in /home/mdg/public_html/modules/views/views_ui.module on line 242.
I am sure I never touched the collation sequence of the db itself. Could a default install of one module be incompatible with another?
Thanks for any clarifications, or help.
Maybe you can check tables
You have utf8_general_ci and utf8_unicode_ci. I'm just guest. For example if your default collations is changed for some reason.
And before it was utf8_general_ci and now it is utf8_unicode_ci if you install a new module it will take new default collation.
Except if in module install these is something special about collation. But I don't believe so.
Finally you can check witch table have different collation and start looking around what can be the reason.
Regards.
Thanks idbl, I think you are
Thanks idbl,
I think you are right. I was hoping it was a bug. I have now observed it on two different sites I manage, in one instance in views (of nodes) and the other instance in the top visitors report... It may have something to do with User tables.
I'll keep looking into it, but it isn't creating any problems on the user side, at the moment, with either situations, so it isn't a priority.
Thanks again,
MidGe
www.ZuNOB.com
Hi again
Hi MidGe, collations is only about char set. Main problem about collation is to start seeing some strange symbols.
There is two thing first is MySQL charset: UTF-8 Unicode (utf8) for example.
And after is collation like this MySQL connection collation: utf8_unicode_ci
I can suggest you to make collations the same.
Regards.
As I thought you were right ldbl :)
It took me till today to fix the issue as I had more pressing ones.
I made all collations at field and at table levels the same using phpMyadmin and the problem, which was only visible to the admin, so wasn't a huge problem, has dissapeared. Took me a while to work out how to change the wrong collations and it was laborious, but it succeeded.
BTW, I am fairly certain there might be a way to write a program script to do this.
www.ZuNOB.com