Bug #114542 | Encoding issue when reusing Prepared Statement | ||
---|---|---|---|
Submitted: | 3 Apr 8:36 | Modified: | 3 Apr 13:18 |
Reporter: | Ian Rolewicz | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Prepared statements | Severity: | S3 (Non-critical) |
Version: | 8.0.36-commercial | OS: | Any (8) |
Assigned to: | CPU Architecture: | Any | |
Tags: | date data type, encoding, Latin1, prepared statement, utf8mb4 |
[3 Apr 8:36]
Ian Rolewicz
[3 Apr 12:18]
MySQL Verification Team
Hi Mr. Rolewicz, Thank you for your bug report. We have run your test case (in SQL and not in Java) with the following releases: * mysql-8.0.32-commercial * mysql-8.0.33-commercial * mysql-8.0.34-commercial * mysql-8.0.35-commercial * mysql-8.0.36-commercial * mysql-8.2.0-commercial * mysql-8.3.0-commercial and in each case we have got the following result: s d NULL 2023-03-01 ü NULL NULL 2023-03-01 ü NULL We tried it also on Oracle Linux and macOS. We are simply not able to repeat it with SQL test case. If you think that this is C/J specific problem, please let us know. Since you are using the Enterprise version of our product, you can also raise an SR on the issue. Can't repeat.
[3 Apr 13:10]
Ian Rolewicz
Thank you for your answer. It might be a Connector/J issue as well, the JDBC connection properties "useCursorFetch=true" and "connectionCollation=latin1_swedish_ci" seem to play a part in this issue. As I noted, we do not have direct access to the MySQL Server console, so we used a client (SQuirrel SQL, which uses Connector/J to connect to the MySQL Server) to send the SQL commands to the server. Could you please try to reproduce the issue with the Java test case ?
[3 Apr 13:18]
MySQL Verification Team
Hi, Actually, you have spotted a problem in your own configuration of the client-side. You have set a connection character set wrongly: connectionCollation=latin1_swedish_ci Hence , your client and connection sides are misconfigured. Configuration of the client and connection side is in the domain of the application programmer and DBA. These are the settings that are under your control. If you read our Reference Manual, you will find out that these are settings that are under your control. Hence, this is not our bug. Not a bug.