Bug #18737 connection default charset doesn't match server default charset
Submitted: 3 Apr 2006 13:51 Modified: 4 May 2006 13:23
Reporter: Mircea LUTIC Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.19 OS:w32
Assigned to: CPU Architecture:Any

[3 Apr 2006 13:51] Mircea LUTIC 
Description:
1. create a database & a table from the command line interface: the charset is (by default) utf8
2. create a C program and execute smth like 
select A,'' from thetbl 
union 
select '',A from thetbl

Illegal mix of collations (utf8_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation 'UNION'

The connection default charset is latin1 while the server default charset is utf8.
:(

How to repeat:
see above

Suggested fix:
have the same default for both (utf8)
[3 Apr 2006 14:21] Mircea LUTIC 
on second examination it seems that the problem is more correctly described as follows: the installation program should configure the my.ini file so that the charset selected by the user is assigned to the default for all of
libmysql.dll , 
server  and 
mysql cmdline
[4 Apr 2006 12:38] Valeriy Kravchuk 
Thank you for a problem report. Please, send your my.ini file content. 

Installer of 5.0.19 on my XP did exactly what you asked for: default-character-set was set to utf8 both in [mysql] and in [mysqld] section.
[4 Apr 2006 12:59] Mircea LUTIC 
I uploaded My-ini.zip for bug 18709 containing several my.ini backups.
The final one worked because I used latin1.

The problem though is not that it doesn't set the same setting for mysql and mysqld. The problem is that when connecting with the C API via *libmysql.dll* I don't get the the same default I chose from the installation.

So if I create a table from mysql cmd line and then execute union statement with libmysql.dll from C it doesn't work.
[4 Apr 2006 13:23] Valeriy Kravchuk 
Please, put defaut-character-set=utf8 just after the [client] section and check again.
[4 May 2006 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".