Bug #90331 | Server does not raise error on unrecognized collation id | ||
---|---|---|---|
Submitted: | 6 Apr 2018 23:28 | Modified: | 6 Sep 2018 18:18 |
Reporter: | Manuel Ung | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: C API (client library) | Severity: | S3 (Non-critical) |
Version: | 5.6 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[6 Apr 2018 23:28]
Manuel Ung
[7 Apr 2018 10:08]
MySQL Verification Team
Hello Manuel Ung, Thank you for the report and feedback. Thanks, Umesh
[20 Apr 2018 2:58]
Manuel Ung
I also found out that this causes functions like mysql_real_escape_string to behave differently, because client will escape assuming utf8mb4 but server is still on latin1.
[6 Sep 2018 18:18]
Paul DuBois
Posted by developer: This was assessed not to be a bug, but the behavior was not described in the docs. It's now explained here: https://dev.mysql.com/doc/refman/8.0/en/charset-connection.html (See the error-handling subsection.) A client that needs to check whether the server honored the requested character set can check the character set using: SELECT @@character_set_client; and if necessary, can select the requested character set using SET NAMES.