| Bug #1841 | Charset problem in 3.x client driver connecting to 4.0 server | ||
|---|---|---|---|
| Submitted: | 14 Nov 2003 11:59 | Modified: | 15 Nov 2003 1:08 |
| Reporter: | Gianluca Sordiglioni | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 3.23.56 | OS: | Linux (Linux) |
| Assigned to: | CPU Architecture: | Any | |
[15 Nov 2003 1:08]
Alexander Keremidarski
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Character sets translation between server and client is implemented in 4.1
[15 Nov 2003 10:29]
Gianluca Sordiglioni
In the documentation: http://www.mysql.com/doc/en/Character_sets.html "When a client connects to a MySQL server, the server sends the default character set in use to the client. The client will switch to use this character set for this connection."
Description: 3.23 clients connecting to MySQL server 4.0 using different character sets obtain incorrect results on string comparison. How to repeat: A query with SUBSTRING(myfield,LOCATE('mystring',x,y),3) always return '' Test environment is: client must be 3.23 version on Linux (charset utf8), server 4.0.16 on FreeBSD (default charset Latin1). Suggested fix: Use client and server with the same charset as temporary solution.