Bug #2366 Wrong utf8 behaviour when data is trancated
Submitted: 13 Jan 2004 2:21 Modified: 10 Feb 2004 4:06
Reporter: Alexander Barkov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.2-bk-current OS:
Assigned to: Alexander Barkov CPU Architecture:Any

[13 Jan 2004 2:21] Alexander Barkov 
Description:
Here's an example of what happens now:

mysql> create table t (s1 char(1) character set utf8);
Query OK, 0 rows affected (0.28 sec)

mysql> insert into t values ('ßß');
Query OK, 1 row affected, 1 warning (0.01 sec)

mysql> select * from t;
+------+
| s1   |
+------+
| ß    |
+------+
1 row in set (0.00 sec)

mysql> select * from t where s1 = 'ß';
Empty set (0.00 sec)

How to repeat:
Run the above.

Suggested fix:
Data trancation should be multi-byte safe.
[6 Feb 2004 5:02] Alexander Barkov 
CHAR type has been fixed.
TEXT still needs fixing.
[10 Feb 2004 4:06] Alexander Barkov 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html