MySQL Bugs: #68701: Server does not support 4-byte encoded UTF8 characters

Bug #68701	Server does not support 4-byte encoded UTF8 characters
Submitted:	18 Mar 2013 12:35	Modified:	28 May 2013 7:45
Reporter:	Remco Tiel	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	5.2.4	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	ODBC SQl Report Builder

Description:
When executing a report in SQL 2012 Report Builder 3.0 with a parameter we're running into the following error:

ERROR [HY000] [MySQL][ODBC 5.2(w) Driver][mysqld-5.1.45-log]Server does not support 4-byte encoded UTF8 characters.

I also tested this with MySQL ODBC Connector 5.1.12 to no avail. We think this is an ODBC issue, yet it could be a SQL Report Builder 3.0 issue.

How to repeat:
Setup:
We set up a ODBC connection to a MySql database with MySQL ODBC Connector 5.2.4 succesfully.
In SQL Report Builder 3.0 we've create a DataSource to the connection succesfully and also created a DataSet succesfully. But when using a parameter in the DataSet things go wrong. Eg we're running the following command in the querybuilder:'select * from customer where email = @email, running this wil not show any records. When using the following command 'select * from customer where email = ?, returns the above error. This happens when the parameter field is set as Text.
However when I set the parameter as Integer and running the following command:select * from customer where ID = ? it will return the record. Yet, when I use 'select * from customer where ID = @ID, no record is returned.

we've also tested the SQL Report Builder 3.0 against a ms sql server and all works fine, therefor we think it's an ODBC connector issue.

Hi Remco,

This is not a bug.
You have the error message because MySQL Server version 5.1.45 does not support the 4-byte UTF8 encoding (utf8mb4). In order to use utf8mb4 you need to install MySQL Server 5.5 or newer.

Please let me know if the problem is still going with the new MySQL Server version.

Thnx for your reply, we will test this in a later stadium...

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".

Remco, this is not a bug since you used wrong server version.

However, if you were to use right server version (one supporting UTF8MB4) you would hit BUG#67297. We will fix the correct problem there.

What do you mean by "wrong server version"? According to http://dev.mysql.com/doc/refman/5.6/en/connector-odbc-versions.html , the 5.2 ODBC connector supports MySQL versions 4.1.1 and higher!!

In this case, the connector doesn't work with Mysql server version 5.1.x, so it is clearly a bug! Former versions of ODBC connector didn't have this problem!