r19200 - gnucash/trunk/src/backend/dbi - Fix #616100 - Incorrect character set used in MySQL backend

[Derek Atkins]

Phil Longstaff <plongstaff at rogers.com> writes:

>> Phil Longstaff <plongstaff at rogers.com> writes:
>>
>>>> > Use "SET NAMES 'utf8'" so that mysql uses utf8 for communication and all
>> char sets.
>>>
>>> In any case, no.  SET NAMES seems to just tell the mysql server that the
>>> char set for all communication with the client is UTF8.  It doesn't
>>> affect the database ifself.
>>
>> What about data already entered into the database?  Will it already be
>> in UTF8?

> The database has already be set up as utf8.  However, if data to be put into
> it was not in utf8 (possibly or probably true without SET NAMES 'utf8'), I
> assume that the data in the database will not be correct.  I'm not sure
> there's anything we can do about that.

Who's top-posting now, Phil?   ;-)

That was my question -- if we notice that the database wasn't configured
with SET NAMES utf8, is there something we can do?

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available