#32384 [Opn->Bgs]: old libmysqlclient caused data loss in MySQL 4.1 DB

ID: 32384 Updated by: sniper@php.net Reported By: ustupkin at mail dot primorye dot ru -Status: Open +Status: Bogus Bug Type: MySQL related Operating System: windows PHP Version: 4.3.10 New Comment: If Mysql breaks backwards compatibility with their own client libs that is hardly a PHP bug. Previous Comments: ------------------------------------------------------------------------ [2005-03-20 15:00:30] ustupkin at mail dot primorye dot ru First I think that it MySQL bug, so "There is an obvious bug in every win32 distribution of MySQL 4.1.x." is wrong ------------------------------------------------------------------------ [2005-03-20 14:59:12] ustupkin at mail dot primorye dot ru Description: ------------ http://bugs.mysql.com/bug.php?id=8420&thanks=2&notify=7 Windows version of PHP 4.x.x compiled with old libmysqlclient - 3.xx.xx. Moreover, it has hardcoded path to mysql charset dir. Reproduce code: --------------- <?php $link = mysql_connect('localhost:3307', 'root', ''); $set = mysql_query('SET NAMES CP1251',$link); $set = mysql_query('SET COLLATION_CONNECTION=CP1251_GENERAL_CI',$link); $charset = mysql_client_encoding($link); printf ("current character set is %s\n", $charset); ?> echoes "File 'c:\mysql\share\charsets\?.conf' not found (Errcode: 22) Character set '#51' is not a compiled character set and is not specified in the 'c:\mysql\share\charsets\Index' file current character set is latin1" There is an obvious bug in every win32 distribution of MySQL 4.1.x. There is no sense to setting such options as: character-sets-dir=c:/mysql/share/charsets default-character-set=cp1251 In any case as result - something like this: File 'c:\mysql\share\charsets\?.conf' not found (Errcode: 22) Character set '#51' is not a compiled character set and is not specified in the 'c:\mysql\share\charsets\Index' file ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=32384&edit=1