diff options
author | Tatiana A. Nurnberg <azundris@mysql.com> | 2009-02-02 18:19:07 +0100 |
---|---|---|
committer | Tatiana A. Nurnberg <azundris@mysql.com> | 2009-02-02 18:19:07 +0100 |
commit | 5622d4261f015a73330d07f50a876304834c5341 (patch) | |
tree | cd452f43ea1c8945f1b415986a36f036ace209aa /mysql-test/t/func_crypt.test | |
parent | 2048bd711797c6197233fa8d36598d0c8d0ef593 (diff) | |
download | mariadb-git-5622d4261f015a73330d07f50a876304834c5341.tar.gz |
Bug#33550: mysqldump 4.0 compatibility broken
mysqldump included character_set_client magic
that is unknown before 4.1 even when asked for
an appropriate compatibility mode.
In compatibility (3.23, 4.0) mode, we do not
output charset statements (not even in a
"comment conditional"), nor do we do magic on
the server, even if the server is sufficient
new (4.1+). Table-names will be output converted
to the charset requested by mysqldump; if such
a conversion is not possible (Ivrit -> Latin),
mysqldump will fail.
Diffstat (limited to 'mysql-test/t/func_crypt.test')
0 files changed, 0 insertions, 0 deletions