[Tickets #8777] Re: $conf['sql']['charset'] is ignored

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8777
------------------------------------------------------------------------------
  Ticket             | 8777
  Updated By         | e.cerny at seznam.cz
  Summary            | $conf['sql']['charset'] is ignored
  Queue              | Horde Base
  Version            | 3.3.5
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


e.cerny at seznam.cz (2009-12-15 15:30) wrote:

> Doesn't matter because we convert the data to the correct charset anyway.

I thought about it and I can say NO YOU DO NOT CONVERT ANYTHING!
The data in database are stored as 8bit representation of multi-byte encoding.
If there was any conversion from mysql  default encoding (latin1,  
which is not able to hold multi-byte characters) to some other  
encoding. It would not obviously work for multi-byte characters.

Horde simply stores utf-8 (if sql-charset is utf8) byte stream in  
mysql as latin1
and the same way retrieves it back.

This bug in combination with php inability to change  
default-character-set for mysql. May be considered not beeing a bug,  
but it is one.
And when php becomes able to set mysql default charset Horde brokes.