[ postfixadmin-Bugs-1828870 ] cannot view a domain page
Brought to you by:
christian_boltz,
gingerdog
From: SourceForge.net <no...@so...> - 2008-04-25 23:01:39
|
Bugs item #1828870, was opened at 2007-11-09 11:16 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828870&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) >Status: Closed >Resolution: Fixed Priority: 9 Private: No Submitted By: frn (frn123) Assigned to: Nobody/Anonymous (nobody) Summary: cannot view a domain page Initial Comment: using and url like http://foo/pa/list-virtual.php?domain=foo.com i get a following error: -- DEBUG INFORMATION: Invalid query: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=' Please check the documentation and website for more information. Postfix Admin Knowledge Base -- Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports. mysql driver. Lookind at the DATABASE_MYSQL.TXT i notice that some of the tables are InnoDB and some MyISAM. MyISAM tables use latin_1 encodoing, InnoDB use utf8. I think all the tables should be innodb/utf8. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-04-26 01:01 Message: Logged In: YES user_id=593261 Originator: NO Fix verified in latest SVN version (r343) by creating a new database. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-04-07 01:31 Message: Logged In: YES user_id=593261 Originator: NO This should be fixed in the latest SVN version (r319). Can you please test it by running upgrade.php? Note: I can't guarantee a clean update. If something goes wrong (you'll see an "Invalid query" message in this case), please drop the table vacation_notification (it contains a list of mail adresses who have received vacation notifications already, so the worst thing that might happen is that some of them receive another one when sending the next mail). ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 23:27 Message: Logged In: YES user_id=593261 Originator: NO Using utf8 everywhere is a bad idea - it wastes some space (a char needs 3 bytes in utf8) and, biger problem, causes problems with the key length in vacation_notification (see bug 1828857). I'll change fields for email addresses to latin1 - mail adresses can't contain utf8 anyway. OTOH, the description fields should really be utf8 because people can enter anything they want there. ---------------------------------------------------------------------- Comment By: frn (frn123) Date: 2007-11-09 11:23 Message: Logged In: YES user_id=1933384 Originator: YES changing all the tables to type innodb made the bug go away with no apparent ill effects (yet?) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828870&group_id=191583 |