[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 18:04) wrote:

> 1. This code is in the PEAR DB package which has nothing to do with Horde.
> 2. The conversion is done to the charset that you configured in your  
> database settings. If this doesn't match the charset that your  
> database is actually using, that's your fault.

No it's you fault because you doesn't set the charset so it's use the  
unchangeable(so far) charset...

The PEAR code we tallk about has changed and you didn't do the  
apropriet change of your code.

PEAR does not set character set on mysql connect anymore (because php  
does not set character set on mysql database connect) so must you...

It's not about what character set my database is using because it's  
about what character set is using the client side. The mysql module in  
php which is default latin1 (UNCHANGEABLE DEFAULT).
It's on application to change it.
I'm telling you that the code that did this right before is doing it  
wrong now because it relays on PEAR functionality that isn't there  
anymore.

Understand ?

And this make this problem a Horde BUG!