On 01/01/2013 06:17 PM, Harald Leithner wrote:
> Hi Thomas,
>
> you are right, the database table character set was latin1_swedish_ci,
> after converting it to utf8_general_ci it works fine. Thx
>
> @Paul what should be the correct character set for all mysql tables?
UTF8 is highly advisable. DBMail will try very hard to work with other
encodings but results will very much depend on the consistency of the
setup. That is where MySQL is very broken (or lax, depending on your
point of view).
> Because mine are mix... I would convert them to utf8 but I'm not sure if
> this is save. Should we correct the mysql update script?
There is no way I know of to safely fix this. Yes, you can do a 'alter
table', but that will *not* change anything in your database. MySQL will
happily work with latin-1 encoded data in a table that is marked as utf8
encoded, and vice versa, etc, etc.
If you run mostly on POP3 or a small user-set, just convert the table
schemas and keep them fingers crossed. People may complain about broken
older messages, but newly inserted data at least will be correct.
Of course doing so, you end up with an inconsistent database but since
MySQL doesn't care about consistency this won't bite you until you try
to migrate to a DBMS that does care. This was a major problem for me
when I switched my main development server from MySQL to PostgreSQL -
data went back to dbmail 1.2 days when encoding wasn't even properly
considered in the codebase.
So: if you can get away with changing everything to UTF8, do so. Else,
at least make sure all encoding settings are consistent.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/[email protected]/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
