Error Number : 1267

[adhmwagde]

Invalid SQL:

SELECT prefix.*, prefixpermission.usergroupid AS restriction
FROM forumprefixset AS forumprefixset
INNER JOIN prefixset AS prefixset ON (prefixset.prefixsetid = forumprefixset.prefixsetid)
INNER JOIN prefix AS prefix ON (prefix.prefixsetid = prefixset.prefixsetid)
LEFT JOIN prefixpermission AS prefixpermission ON (prefix.prefixid = prefixpermission.prefixid)
WHERE forumprefixset.forumid = 2
ORDER BY prefixset.displayorder, prefix.displayorder;

MySQL Error : Illegal mix of collations (latin1_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '='
Error Number : 1267
Request Date : Thursday, January 8th 2009 @ 11:21:50 PM
Error Date : Thursday, January 8th 2009 @ 11:21:50 PM
Script : http://www.alshohooh.ws/vb/newthread.php?do=newthread&f=2
Referrer : http://www.alshohooh.ws/vb/forumdisplay.php?f=2
IP Address : 41.178.144.86
Username : الدعم الفني
Classname : vB_Database
MySQL Version : 5.0.51a-community

[Bellardia]

All your tables should have the same collation, the vb default is latin1_swedish_ci.

[UKBusinessLive]

Thats Right, This is from Wayne Luke over at the VBulletin.com site

All tables and fields should be the same collation to prevent this error from occuring in the future. It can occur on other queries not just when upgrading if there are mixed collations. When vBulletin creates new tables and fields it will use the default of the database for the collation. This is usually latin1_general_ci unless you change it. You can see instructions on how to change a database's collation settings in the MySQL manual.

;)