On Mon, 2007-05-14 at 02:51 +0300, Aleksander wrote: > Paul J Stevens wrote: > > > Mysql and postgresql users using anything but ENCODING=utf8 should take > > notice. Dbmail uses utf8 internally because gmime uses utf8 internally. > > You should do too. Convert your databases if you can, or plan to do so > > soon. Unicode and its UTF8 representation are the future. > > > > Converting your mysql database is trivial, but takes time and table > > locks (making the database read-only). A couple of 'ALTER' statements > > got me going just fine. > > Sounds good, but which collation should we use? > http://dev.mysql.com/doc/refman/5.0/en/charset-unicode-sets.html > > There's utf8_bin, utf8_general_ci (default), utf8_unicode_ci and for me > there's utf8_estonian_ci too.
We issue only a "SET NAMES 'encoding'" without the COLLATION argument, so at the moment we fall onto whatever default the database has, but... Unless Paul changed any queries with the major utf8 cleanup today, the database collation doesn't matter because we don't ask the database to do any sorting on utf8 columns; all of the sorting takes place on the DBMail side in concert with GMime. Aaron _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
