mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-23 15:24:16 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test/suite/jp/t/jp_convert_ujis.test

96 lines
4.1 KiB
Text
Raw Normal View History

Fix for Bug#28563 Test suite "jp" fails completely - The main goal of this fix is to make the "jp" suite runnable in general and to make it more robust for use in pushbuild under build team conditions. - It was decided to fix the remaining heavy issues within the architecture of this test later (-> WL 4327 Redesign the 'jp' testsuite for build team testing conditions) Only the test jp_trim_sjis got some significant improvements of its architecture (Just as proof of concept for the other tests). - Tests suffering from Bug 36597 Testsuite "jp": Suspicious results for some tests (unexpected result sets) were disabled - *.opt files were used to avoid differences on OS (Windows) because of case sensitive tablenames within the tests
2008-05-15 18:01:13 +02:00
--source include/have_sjis.inc
--source include/have_ucs2.inc
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
--source include/have_ujis.inc
Fix for Bug#28563 Test suite "jp" fails completely - The main goal of this fix is to make the "jp" suite runnable in general and to make it more robust for use in pushbuild under build team conditions. - It was decided to fix the remaining heavy issues within the architecture of this test later (-> WL 4327 Redesign the 'jp' testsuite for build team testing conditions) Only the test jp_trim_sjis got some significant improvements of its architecture (Just as proof of concept for the other tests). - Tests suffering from Bug 36597 Testsuite "jp": Suspicious results for some tests (unexpected result sets) were disabled - *.opt files were used to avoid differences on OS (Windows) because of case sensitive tablenames within the tests
2008-05-15 18:01:13 +02:00
--source include/have_utf8.inc
--source include/have_innodb.inc
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
--disable_warnings
drop table if exists `<60>ԣ<EFBFBD>`;
drop table if exists `<60>ԣ<EFBFBD>`;
drop table if exists `<60>ԣ<EFBFBD>`;
drop table if exists `<60>ԣ<EFBFBD>`;
drop table if exists `<60>ԣ<EFBFBD>`;
drop table if exists `<60>ԣ<EFBFBD>`;
drop table if exists `<60>ԣ<EFBFBD>`;
drop table if exists `<60>ԣ<EFBFBD>`;
drop table if exists `<60>ԣ<EFBFBD>`;
--enable_warnings
#
# Test CONVERT() function with Japanese character in ujis encoding
#
SET NAMES ujis;
SET character_set_database = ujis;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` char(20), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ujis engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` char(20), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ujis engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` char(20), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ujis engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` char(20), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ujis engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` char(20), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ujis engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` char(20), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ujis engine = myisam;
Fix for Bug#28563 Test suite "jp" fails completely - The main goal of this fix is to make the "jp" suite runnable in general and to make it more robust for use in pushbuild under build team conditions. - It was decided to fix the remaining heavy issues within the architecture of this test later (-> WL 4327 Redesign the 'jp' testsuite for build team testing conditions) Only the test jp_trim_sjis got some significant improvements of its architecture (Just as proof of concept for the other tests). - Tests suffering from Bug 36597 Testsuite "jp": Suspicious results for some tests (unexpected result sets) were disabled - *.opt files were used to avoid differences on OS (Windows) because of case sensitive tablenames within the tests
2008-05-15 18:01:13 +02:00
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` char(20), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ujis engine = MEMORY;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` char(20), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ujis engine = MEMORY;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` char(20), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ujis engine = MEMORY;
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
#Load the following data in each table
# jisx0201 hankaku-katakana data
# jisx0208 data
# jisx0212 supplemental character data
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0201_ujis.dat' INTO TABLE `<60>ԣ<EFBFBD>`;
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0208_ujis.dat' INTO TABLE `<60>ԣ<EFBFBD>`;
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0212_ujis.dat' INTO TABLE `<60>ԣ<EFBFBD>`;
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0201_ujis.dat' INTO TABLE `<60>ԣ<EFBFBD>`;
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0208_ujis.dat' INTO TABLE `<60>ԣ<EFBFBD>`;
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0212_ujis.dat' INTO TABLE `<60>ԣ<EFBFBD>`;
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0201_ujis.dat' INTO TABLE `<60>ԣ<EFBFBD>`;
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0208_ujis.dat' INTO TABLE `<60>ԣ<EFBFBD>`;
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0212_ujis.dat' INTO TABLE `<60>ԣ<EFBFBD>`;
#InnoDB
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using utf8) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using ucs2) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using sjis) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using utf8) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using ucs2) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using sjis) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using utf8) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using ucs2) FROM `<60>ԣ<EFBFBD>`;
# The result will get garbled because jisx0212 is not included in sjis
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using sjis) FROM `<60>ԣ<EFBFBD>`;
#MyISAM
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using utf8) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using ucs2) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using sjis) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using utf8) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using ucs2) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using sjis) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using utf8) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using ucs2) FROM `<60>ԣ<EFBFBD>`;
# The result will get garbled because jisx0212 is not included in sjis
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using sjis) FROM `<60>ԣ<EFBFBD>`;
Fix for Bug#28563 Test suite "jp" fails completely - The main goal of this fix is to make the "jp" suite runnable in general and to make it more robust for use in pushbuild under build team conditions. - It was decided to fix the remaining heavy issues within the architecture of this test later (-> WL 4327 Redesign the 'jp' testsuite for build team testing conditions) Only the test jp_trim_sjis got some significant improvements of its architecture (Just as proof of concept for the other tests). - Tests suffering from Bug 36597 Testsuite "jp": Suspicious results for some tests (unexpected result sets) were disabled - *.opt files were used to avoid differences on OS (Windows) because of case sensitive tablenames within the tests
2008-05-15 18:01:13 +02:00
#MEMORY
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using utf8) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using ucs2) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using sjis) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using utf8) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using ucs2) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using sjis) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using utf8) FROM `<60>ԣ<EFBFBD>`;
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using ucs2) FROM `<60>ԣ<EFBFBD>`;
# The result will get garbled because jisx0212 is not included in sjis
SELECT `<60>ã<EFBFBD>`, CONVERT(`<60>ã<EFBFBD>` using sjis) FROM `<60>ԣ<EFBFBD>`;
drop table `<60>ԣ<EFBFBD>`;
drop table `<60>ԣ<EFBFBD>`;
drop table `<60>ԣ<EFBFBD>`;
drop table `<60>ԣ<EFBFBD>`;
drop table `<60>ԣ<EFBFBD>`;
drop table `<60>ԣ<EFBFBD>`;
drop table `<60>ԣ<EFBFBD>`;
drop table `<60>ԣ<EFBFBD>`;
drop table `<60>ԣ<EFBFBD>`;
Reference in a new issue Copy permalink