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

120 lines
3.6 KiB
Text
Raw Normal View History

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_ucs2.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_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
# half-with kana is not handled correctly in 4.1
# because of bug #5174
# It will be fixed in 5.0
--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 ENUM values with Japanese characters in ucs2 encoding
#
SET NAMES ujis;
SET character_set_database = ucs2;
SET collation_connection = ucs2_general_ci;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` ENUM('<27><>','<27><>','<27><>'), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ucs2 engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` ENUM('<27><>','<27><>','<27><>'), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ucs2 engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` ENUM('<27><><EFBFBD>','<27><><EFBFBD>','<27><><EFBFBD>'), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ucs2 engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` ENUM('<27><>','<27><>','<27><>'), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ucs2 engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` ENUM('<27><>','<27><>','<27><>'), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ucs2 engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` ENUM('<27><><EFBFBD>','<27><><EFBFBD>','<27><><EFBFBD>'), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ucs2 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>` ENUM('<27><>','<27><>','<27><>'), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ucs2 engine = MEMORY;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` ENUM('<27><>','<27><>','<27><>'), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ucs2 engine = MEMORY;
CREATE TABLE `<60>ԣ<EFBFBD>` (`<60>ã<EFBFBD>` ENUM('<27><><EFBFBD>','<27><><EFBFBD>','<27><><EFBFBD>'), INDEX(`<60>ã<EFBFBD>`)) DEFAULT CHARSET = ucs2 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>ԣ<EFBFBD>` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>` VALUES ('<27><><EFBFBD>'),('<27><><EFBFBD>'),('<27><><EFBFBD>');
INSERT INTO `<60>ԣ<EFBFBD>` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>` VALUES ('<27><><EFBFBD>'),('<27><><EFBFBD>'),('<27><><EFBFBD>');
INSERT INTO `<60>ԣ<EFBFBD>` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>` VALUES ('<27><><EFBFBD>'),('<27><><EFBFBD>'),('<27><><EFBFBD>');
SELECT * FROM `<60>ԣ<EFBFBD>`;
SELECT * FROM `<60>ԣ<EFBFBD>`;
SELECT * FROM `<60>ԣ<EFBFBD>`;
SELECT * FROM `<60>ԣ<EFBFBD>`;
SELECT * FROM `<60>ԣ<EFBFBD>`;
SELECT * FROM `<60>ԣ<EFBFBD>`;
SELECT * FROM `<60>ԣ<EFBFBD>`;
SELECT * FROM `<60>ԣ<EFBFBD>`;
SELECT * FROM `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
#
# Test problem with enum values after the colum with NOT NULL restriction
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
# Bug#7302 UCS2 data in ENUM field get truncated when new column is added
ALTER TABLE `<60>ԣ<EFBFBD>` ADD `<60>ã<EFBFBD>` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>ԣ<EFBFBD>` ADD `<60>ã<EFBFBD>` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>ԣ<EFBFBD>` ADD `<60>ã<EFBFBD>` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>ԣ<EFBFBD>` ADD `<60>ã<EFBFBD>` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>ԣ<EFBFBD>` ADD `<60>ã<EFBFBD>` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>ԣ<EFBFBD>` ADD `<60>ã<EFBFBD>` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>ԣ<EFBFBD>` ADD `<60>ã<EFBFBD>` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>ԣ<EFBFBD>` ADD `<60>ã<EFBFBD>` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>ԣ<EFBFBD>` ADD `<60>ã<EFBFBD>` CHAR(1) NOT NULL FIRST;
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
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
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
SHOW CREATE TABLE `<60>ԣ<EFBFBD>`;
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
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
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
DESC `<60>ԣ<EFBFBD>`;
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
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