diff options
| author | aelkin@mysql.com <> | 2006-02-09 16:23:09 +0200 |
|---|---|---|
| committer | aelkin@mysql.com <> | 2006-02-09 16:23:09 +0200 |
| commit | dd2a44c497b5fe24a4f2744d5f2b6fafd1cebbfd (patch) | |
| tree | 62a885bef438849f6bce8103b589c4944703fe7e /mysql-test/r/mysql.result | |
| parent | 3b0dcb08a4130052857ed9dceb47307c57be7733 (diff) | |
| download | mariadb-git-dd2a44c497b5fe24a4f2744d5f2b6fafd1cebbfd.tar.gz | |
BUG#16217 forced to introduce a separate mysql client command to adopt its
internal charset to one associated with currently being handled query.
To note such a query can come from interactive client either.
There was a discussion within replication team and Monty who's suggestion won.
It avoids straightforward parsing of all `set' queries that could affect client side
character set.
According to the idea, mysql client does not parse `set' queries but rather cares of
`charset new_cs_name' command.
This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion)
so that enlightened clients like `mysql' knows what to do with it.
Interactive human can switch between many multi-byte charsets during the session
providing the command explicitly.
To note that setting new internal mysql's charset does not
trigger sending any `SET' sql statement to the server.
Diffstat (limited to 'mysql-test/r/mysql.result')
| -rw-r--r-- | mysql-test/r/mysql.result | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/mysql-test/r/mysql.result b/mysql-test/r/mysql.result index 76faa12373a..611813d9c3f 100644 --- a/mysql-test/r/mysql.result +++ b/mysql-test/r/mysql.result @@ -59,3 +59,13 @@ database() test unlock tables; drop table t1; +ソ +ソ +c_cp932 +ソ +ソ +ソ +ソ +ソ +ソ +ソ |