Re[2]: [PHP-DB] 'Illegal mix of collations' with PHP 4.3.10 and MySQL 4.1.7

[cut] DG> I've got the same problem with PHP 5.0.2 and MySQL 4.1.8. I asked this DG> question many times on different mailing lists but still haven't got DG> satisfactory answer... That's the problem, I've reviewed different mailing lists as well but saw no reply... all problems that were presented regarding collation / charset were just simple "I converted to MySQL 4.1 and now my queries won't work" problems :/ [cut] DG> AFAIK have to be DG> default-character-set=latin2 DG> at least this works for 'mysql' utility. This generates an error for my system (unknown configuration option "default-character-set"). This option works for the mysqld entry (the server), but not for the clients. I read this solution (character_set) in some mailing list reply. What's funny, when I did it, it SEEMED to work - PHP started crashing complaining about the lack of the latin2/Index.xml file. When I made a link to the file and added an additional entry for charset-default-dir, it stopped complaining... but didn't exactly start working :P [cut] DG> Will have no effect. So I've noticed :) DG> The thing is that source code of libmysql.dll/libmysqli.dll DOESN'T contain DG> code for setting connection charset (as I was said on the MySQL list). So DG> what we want seems to be impossible. Well, the problem is, it DID work. I mean, I know a solution would be to recompile libmysql.dll and add the default charset in it, but what I mean is not using a default, arbitrarily chosen character set, but chosing the character set implied by the locale or server default character set (or database default character set). DG> Are there any comments from libmysql.dll/libmysqli.dll developers? I have not bothered them yet, I still don't know if this is a bug or just a configuration problem on my side :( -- Greetings, Piotr Wilkin pwl@druid.com.pl PGP key: http://pwl.yz.pl/pwlpgp.txt