On Sat, 2007-05-12 at 12:44 +0200, Peter Rabbitson wrote: > Aaron Stone wrote: > > On Sat, 2007-05-12 at 11:15 +0200, Peter Rabbitson wrote: > >> Peter Rabbitson wrote: > >>> In case that encoding=utf8, what collation does dbmail expect in the > >>> mysql database? Does it matter if it is any of the case insensitive ones > >>> or should it be the bin? Thanks > >>> > >> To answer my own question: I tried with utf8_bin, and got > >> dbmysql.c,db_mysql_check_collations(+116): does > >> [collation_database:utf8_bin] match [collation_connection:utf8_general_ci]? > >> > >> I guess the only supported collation is general_ci, since there is no > >> corresponding setting in dbmail.conf. > >> > >> Excuse the noise :) > > > > The corresponding setting in dbmail.conf is also utf8_bin ;-) > > We just pass this value along to MySQL, it is not used internally. > > > > Erm... so how is the dbmail.conf setting called then? There is > 'encoding' for database encoding and for collation there is...?
The MySQL query we issue is "SET NAMES <encodingvalue>" """ Setting character_set_connection to x also sets collation_connection to the default collation for x. It is not necessary to set that collation explicitly. To specify a particular collation for the character sets, use the optional COLLATE clause: """ http://dev.mysql.com/doc/refman/5.0/en/charset-connection.html I tried setting dbmail.conf: "encoding=utf8_bin" on my dev machine, and MySQL reported that this was not a valid character set. Of course - it's only a collation, not a character set. So it has to go in with the query "SET NAMES 'utf8' COLLATE 'utf8_bin'". We'd need a new dbmail.conf entry to enable this. It's very simple to add this, but I need to know, do we actually need it? Aaron _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
