summaryrefslogtreecommitdiff
path: root/tests/mysql_client_test.c
diff options
context:
space:
mode:
authorunknown <anozdrin/alik@ibm.>2007-06-28 13:24:52 +0400
committerunknown <anozdrin/alik@ibm.>2007-06-28 13:24:52 +0400
commit925c33db65a6dcfdf21bd0b047702e7e7221dd89 (patch)
treebc5b66df7f78f1cc952076ff6eb5690b7db19d1d /tests/mysql_client_test.c
parent6f059005ef975f2a508713f7631138f7f07a2f97 (diff)
downloadmariadb-git-925c33db65a6dcfdf21bd0b047702e7e7221dd89.tar.gz
Fix for BUG#10491: Server returns data as charset binary
SHOW CREATE TABLE or SELECT FROM I_S. Actually, the bug discovers two problems: - the original query is not preserved properly. This is the problem of BUG#16291; - the resultset of SHOW CREATE TABLE statement is binary. This patch fixes the second problem for the 5.0. Both problems will be fixed in 5.1. mysql-test/r/show_check.result: Update result file. mysql-test/t/show_check.test: Provide test case for BUG#10491. sql/item.h: Use utf8_general_ci instead of binary collation by default, because for views and base tables utf8 is the character set in which their definition is stored. For system constants it's the default character set, and for other objects (routines, triggers), no character set is stored, and therefore no character set is known, so returning utf8 is just as good as any non-binary character set. This latter problem is fixed in 5.1 by 16291. In 5.1 we will return the "real" character set.
Diffstat (limited to 'tests/mysql_client_test.c')
0 files changed, 0 insertions, 0 deletions