diff options
| author | unknown <guilhem@mysql.com> | 2004-06-08 19:55:04 +0200 |
|---|---|---|
| committer | unknown <guilhem@mysql.com> | 2004-06-08 19:55:04 +0200 |
| commit | 7bd8167fb703aea4f3d533441a26a9dbc628a258 (patch) | |
| tree | dfd35579ab497716486cb24c5991ab22ff0141f0 /vio/test-sslserver.c | |
| parent | 8ab01b335d502730bef01764d0cd4adae6f86ee0 (diff) | |
| download | mariadb-git-7bd8167fb703aea4f3d533441a26a9dbc628a258.tar.gz | |
Correction to replication of charsets in 4.1:
In mysqlbinlog, there was a problem with how we escaped the content of a string user variable.
To be perfect, we should have escaped with character_set_client. But this charset is unknown
to mysqlbinlog. So the simplest is to print the string in hex. This is unreadable but
100% safe with any charset (checked with Bar), no more need to bother with character_set_client.
mysql-test/r/rpl_charset.result:
hex strings
mysql-test/r/rpl_user_variables.result:
hex strings
mysql-test/r/user_var.result:
hex strings
sql/log_event.cc:
In mysqlbinlog, there was a problem with how we escaped the content of a string user variable.
To be perfect, we should have escaped with character_set_client. But this charset is unknown
to mysqlbinlog. So the simplest is to print the string in hex. This is unreadable but
100% safe with any charset (checked with Bar), no more need to bother with character_set_client.
Diffstat (limited to 'vio/test-sslserver.c')
0 files changed, 0 insertions, 0 deletions