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

67 lines
2.6 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_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
--character_set sjis
--disable_warnings
drop table if exists `<60>s<EFBFBD>P`;
drop table if exists `<60>s<EFBFBD>Q`;
drop table if exists `<60>s<EFBFBD>R`;
drop table if exists `<60>s<EFBFBD>S`;
drop table if exists `<60>s<EFBFBD>T`;
drop table if exists `<60>s<EFBFBD>U`;
drop table if exists `<60>s<EFBFBD>V`;
drop table if exists `<60>s<EFBFBD>W`;
drop table if exists `<60>s<EFBFBD>X`;
--enable_warnings
#
# Test CHAR_LENGTH() function with Japanese character in sjis encoding
#
SET NAMES sjis;
SET character_set_database = sjis;
CREATE TABLE `<60>s<EFBFBD>P` (`<60>b<EFBFBD>P` char(5), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = innodb;
CREATE TABLE `<60>s<EFBFBD>Q` (`<60>b<EFBFBD>P` char(5), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = innodb;
CREATE TABLE `<60>s<EFBFBD>R` (`<60>b<EFBFBD>P` char(5), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = innodb;
CREATE TABLE `<60>s<EFBFBD>S` (`<60>b<EFBFBD>P` char(5), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = myisam;
CREATE TABLE `<60>s<EFBFBD>T` (`<60>b<EFBFBD>P` char(5), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = myisam;
CREATE TABLE `<60>s<EFBFBD>U` (`<60>b<EFBFBD>P` char(5), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis 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>s<EFBFBD>V` (`<60>b<EFBFBD>P` char(5), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = MEMORY;
CREATE TABLE `<60>s<EFBFBD>W` (`<60>b<EFBFBD>P` char(5), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = MEMORY;
CREATE TABLE `<60>s<EFBFBD>X` (`<60>b<EFBFBD>P` char(5), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis 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
INSERT INTO `<60>s<EFBFBD>P` VALUES ('<27><><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD>'),('<27><><EFBFBD>'),('<27><>'),('<27>'),('');
INSERT INTO `<60>s<EFBFBD>Q` VALUES ('<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD>'),('<27><>'),('');
INSERT INTO `<60>s<EFBFBD>R` VALUES ('<27>\<5C>\<5C>\<5C>\<5C>\'),('<27>\<5C>\<5C>\<5C>\'),('<27>\<5C>\<5C>\'),('<27>\<5C>\'),('<27>\'),('');
INSERT INTO `<60>s<EFBFBD>S` VALUES ('<27><><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD>'),('<27><><EFBFBD>'),('<27><>'),('<27>'),('');
INSERT INTO `<60>s<EFBFBD>T` VALUES ('<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD>'),('<27><>'),('');
INSERT INTO `<60>s<EFBFBD>U` VALUES ('<27>\<5C>\<5C>\<5C>\<5C>\'),('<27>\<5C>\<5C>\<5C>\'),('<27>\<5C>\<5C>\'),('<27>\<5C>\'),('<27>\'),('');
INSERT INTO `<60>s<EFBFBD>V` VALUES ('<27><><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD>'),('<27><><EFBFBD>'),('<27><>'),('<27>'),('');
INSERT INTO `<60>s<EFBFBD>W` VALUES ('<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>'),('<27><><EFBFBD><EFBFBD>'),('<27><>'),('');
INSERT INTO `<60>s<EFBFBD>X` VALUES ('<27>\<5C>\<5C>\<5C>\<5C>\'),('<27>\<5C>\<5C>\<5C>\'),('<27>\<5C>\<5C>\'),('<27>\<5C>\'),('<27>\'),('');
#InnoDB
SELECT `<60>b<EFBFBD>P`, CHAR_LENGTH(`<60>b<EFBFBD>P`) FROM `<60>s<EFBFBD>P`;
SELECT `<60>b<EFBFBD>P`, CHAR_LENGTH(`<60>b<EFBFBD>P`) FROM `<60>s<EFBFBD>Q`;
SELECT `<60>b<EFBFBD>P`, CHAR_LENGTH(`<60>b<EFBFBD>P`) FROM `<60>s<EFBFBD>R`;
#MyISAM
SELECT `<60>b<EFBFBD>P`, CHAR_LENGTH(`<60>b<EFBFBD>P`) FROM `<60>s<EFBFBD>S`;
SELECT `<60>b<EFBFBD>P`, CHAR_LENGTH(`<60>b<EFBFBD>P`) FROM `<60>s<EFBFBD>T`;
SELECT `<60>b<EFBFBD>P`, CHAR_LENGTH(`<60>b<EFBFBD>P`) FROM `<60>s<EFBFBD>U`;
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>b<EFBFBD>P`, CHAR_LENGTH(`<60>b<EFBFBD>P`) FROM `<60>s<EFBFBD>V`;
SELECT `<60>b<EFBFBD>P`, CHAR_LENGTH(`<60>b<EFBFBD>P`) FROM `<60>s<EFBFBD>W`;
SELECT `<60>b<EFBFBD>P`, CHAR_LENGTH(`<60>b<EFBFBD>P`) FROM `<60>s<EFBFBD>X`;
DROP TABLE `<60>s<EFBFBD>P`;
DROP TABLE `<60>s<EFBFBD>Q`;
DROP TABLE `<60>s<EFBFBD>R`;
DROP TABLE `<60>s<EFBFBD>S`;
DROP TABLE `<60>s<EFBFBD>T`;
DROP TABLE `<60>s<EFBFBD>U`;
DROP TABLE `<60>s<EFBFBD>V`;
DROP TABLE `<60>s<EFBFBD>W`;
DROP TABLE `<60>s<EFBFBD>X`;
Reference in a new issue Copy permalink