Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
23.08.3
-
None
-
MXS-SPRINT-198, MXS-SPRINT-199
Description
If client sends a character set during connection handshake, MaxScale sends a different character set in connection handshake ok packet.
Code:
static int test_maxscale_charset(MYSQL *unused __attribute__(unused))
|
{
|
const char *cs_test= "latin2";
|
MYSQL *mysql= mysql_init(NULL);
|
mysql_options(mysql, MYSQL_SET_CHARSET_NAME, cs_test);
|
|
FAIL_IF(!my_test_connect(mysql, hostname, username,
|
password, schema, port, socketname, 0),
|
mysql_error(mysql));
|
diag("Character set changed from %s to %s", cs_test, mysql_character_set_name(mysql));
|
FAIL_IF(strcmp(mysql_character_set_name(mysql), cs_test), "Wrong character set name");
|
|
mysql_close(mysql);
|
return OK;
|
}
|
Output:
# Character set changed from latin2 to utf8mb4
|
# Error: Wrong character set name
|
Attachments
Issue Links
- is duplicated by
-
MXS-4955 Character set 'utf8mb3' is not supported
- Closed