mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-02-01 19:41:47 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test/suite/jp/r/jp_enum_sjis.result

280 lines
7.8 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
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`;
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
drop table if exists t1;
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
SET NAMES sjis;
SET character_set_database = sjis;
CREATE TABLE `<60>s<EFBFBD>P` (`<60>b<EFBFBD>P` ENUM('<27>','<27>','<27>'), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = innodb;
CREATE TABLE `<60>s<EFBFBD>Q` (`<60>b<EFBFBD>P` ENUM('<27><>','<27><>','<27><>'), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = innodb;
CREATE TABLE `<60>s<EFBFBD>R` (`<60>b<EFBFBD>P` ENUM('<27>\','<27>\','<27>\'), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = innodb;
CREATE TABLE `<60>s<EFBFBD>S` (`<60>b<EFBFBD>P` ENUM('<27>','<27>','<27>'), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = myisam;
CREATE TABLE `<60>s<EFBFBD>T` (`<60>b<EFBFBD>P` ENUM('<27><>','<27><>','<27><>'), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = myisam;
CREATE TABLE `<60>s<EFBFBD>U` (`<60>b<EFBFBD>P` ENUM('<27>\','<27>\','<27>\'), 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` ENUM('<27>','<27>','<27>'), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = MEMORY;
CREATE TABLE `<60>s<EFBFBD>W` (`<60>b<EFBFBD>P` ENUM('<27><>','<27><>','<27><>'), INDEX(`<60>b<EFBFBD>P`)) DEFAULT CHARSET = sjis engine = MEMORY;
CREATE TABLE `<60>s<EFBFBD>X` (`<60>b<EFBFBD>P` ENUM('<27>\','<27>\','<27>\'), 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>'),('<27>'),('<27>');
INSERT INTO `<60>s<EFBFBD>Q` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>s<EFBFBD>R` VALUES ('<27>\'),('<27>\'),('<27>\');
INSERT INTO `<60>s<EFBFBD>S` VALUES ('<27>'),('<27>'),('<27>');
INSERT INTO `<60>s<EFBFBD>T` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>s<EFBFBD>U` VALUES ('<27>\'),('<27>\'),('<27>\');
INSERT INTO `<60>s<EFBFBD>V` VALUES ('<27>'),('<27>'),('<27>');
INSERT INTO `<60>s<EFBFBD>W` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>s<EFBFBD>X` VALUES ('<27>\'),('<27>\'),('<27>\');
SELECT * FROM `<60>s<EFBFBD>P`;
<EFBFBD>b<EFBFBD>P
<EFBFBD>
<EFBFBD>
<EFBFBD>
SELECT * FROM `<60>s<EFBFBD>Q`;
<EFBFBD>b<EFBFBD>P
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
SELECT * FROM `<60>s<EFBFBD>R`;
<EFBFBD>b<EFBFBD>P
<EFBFBD>\
<EFBFBD>\
<EFBFBD>\
SELECT * FROM `<60>s<EFBFBD>S`;
<EFBFBD>b<EFBFBD>P
<EFBFBD>
<EFBFBD>
<EFBFBD>
SELECT * FROM `<60>s<EFBFBD>T`;
<EFBFBD>b<EFBFBD>P
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
SELECT * FROM `<60>s<EFBFBD>U`;
<EFBFBD>b<EFBFBD>P
<EFBFBD>\
<EFBFBD>\
<EFBFBD>\
SELECT * FROM `<60>s<EFBFBD>V`;
<EFBFBD>b<EFBFBD>P
<EFBFBD>
<EFBFBD>
<EFBFBD>
SELECT * FROM `<60>s<EFBFBD>W`;
<EFBFBD>b<EFBFBD>P
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
SELECT * FROM `<60>s<EFBFBD>X`;
<EFBFBD>b<EFBFBD>P
<EFBFBD>\
<EFBFBD>\
<EFBFBD>\
SHOW CREATE TABLE `<60>s<EFBFBD>P`;
Table Create Table
<EFBFBD>s<EFBFBD>P CREATE TABLE `<60>s<EFBFBD>P` (
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
`<60>b<EFBFBD>P` enum('<27>','<27>','<27>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>Q`;
Table Create Table
<EFBFBD>s<EFBFBD>Q CREATE TABLE `<60>s<EFBFBD>Q` (
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
`<60>b<EFBFBD>P` enum('<27><>','<27><>','<27><>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>R`;
Table Create Table
<EFBFBD>s<EFBFBD>R CREATE TABLE `<60>s<EFBFBD>R` (
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
`<60>b<EFBFBD>P` enum('<27>\','<27>\','<27>\') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>S`;
Table Create Table
<EFBFBD>s<EFBFBD>S CREATE TABLE `<60>s<EFBFBD>S` (
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
`<60>b<EFBFBD>P` enum('<27>','<27>','<27>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>T`;
Table Create Table
<EFBFBD>s<EFBFBD>T CREATE TABLE `<60>s<EFBFBD>T` (
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
`<60>b<EFBFBD>P` enum('<27><>','<27><>','<27><>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>U`;
Table Create Table
<EFBFBD>s<EFBFBD>U CREATE TABLE `<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
`<60>b<EFBFBD>P` enum('<27>\','<27>\','<27>\') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>V`;
Table Create Table
<EFBFBD>s<EFBFBD>V CREATE TABLE `<60>s<EFBFBD>V` (
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
`<60>b<EFBFBD>P` enum('<27>','<27>','<27>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
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
) ENGINE=MEMORY DEFAULT CHARSET=sjis
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
SHOW CREATE TABLE `<60>s<EFBFBD>W`;
Table Create Table
<EFBFBD>s<EFBFBD>W CREATE TABLE `<60>s<EFBFBD>W` (
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
`<60>b<EFBFBD>P` enum('<27><>','<27><>','<27><>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
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
) ENGINE=MEMORY DEFAULT CHARSET=sjis
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
SHOW CREATE TABLE `<60>s<EFBFBD>X`;
Table Create Table
<EFBFBD>s<EFBFBD>X CREATE TABLE `<60>s<EFBFBD>X` (
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
`<60>b<EFBFBD>P` enum('<27>\','<27>\','<27>\') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
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
) ENGINE=MEMORY DEFAULT CHARSET=sjis
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
DESC `<60>s<EFBFBD>P`;
Field Type Null Key Default Extra
<EFBFBD>b<EFBFBD>P enum('<27>','<27>','<27>') YES MUL NULL
DESC `<60>s<EFBFBD>Q`;
Field Type Null Key Default Extra
<EFBFBD>b<EFBFBD>P enum('<27><>','<27><>','<27><>') YES MUL NULL
DESC `<60>s<EFBFBD>R`;
Field Type Null Key Default Extra
<EFBFBD>b<EFBFBD>P enum('<27>\','<27>\','<27>\') YES MUL NULL
DESC `<60>s<EFBFBD>S`;
Field Type Null Key Default Extra
<EFBFBD>b<EFBFBD>P enum('<27>','<27>','<27>') YES MUL NULL
DESC `<60>s<EFBFBD>T`;
Field Type Null Key Default Extra
<EFBFBD>b<EFBFBD>P enum('<27><>','<27><>','<27><>') YES MUL NULL
DESC `<60>s<EFBFBD>U`;
Field Type Null Key Default Extra
<EFBFBD>b<EFBFBD>P enum('<27>\','<27>\','<27>\') YES MUL NULL
DESC `<60>s<EFBFBD>V`;
Field Type Null Key Default Extra
<EFBFBD>b<EFBFBD>P enum('<27>','<27>','<27>') YES MUL NULL
DESC `<60>s<EFBFBD>W`;
Field Type Null Key Default Extra
<EFBFBD>b<EFBFBD>P enum('<27><>','<27><>','<27><>') YES MUL NULL
DESC `<60>s<EFBFBD>X`;
Field Type Null Key Default Extra
<EFBFBD>b<EFBFBD>P enum('<27>\','<27>\','<27>\') YES MUL NULL
ALTER TABLE `<60>s<EFBFBD>P` ADD `<60>b<EFBFBD>Q` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>s<EFBFBD>Q` ADD `<60>b<EFBFBD>Q` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>s<EFBFBD>R` ADD `<60>b<EFBFBD>Q` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>s<EFBFBD>S` ADD `<60>b<EFBFBD>Q` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>s<EFBFBD>T` ADD `<60>b<EFBFBD>Q` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>s<EFBFBD>U` ADD `<60>b<EFBFBD>Q` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>s<EFBFBD>V` ADD `<60>b<EFBFBD>Q` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>s<EFBFBD>W` ADD `<60>b<EFBFBD>Q` CHAR(1) NOT NULL FIRST;
ALTER TABLE `<60>s<EFBFBD>X` ADD `<60>b<EFBFBD>Q` CHAR(1) NOT NULL FIRST;
SHOW CREATE TABLE `<60>s<EFBFBD>P`;
Table Create Table
<EFBFBD>s<EFBFBD>P CREATE TABLE `<60>s<EFBFBD>P` (
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
`<60>b<EFBFBD>Q` char(1) NOT NULL,
`<60>b<EFBFBD>P` enum('<27>','<27>','<27>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>Q`;
Table Create Table
<EFBFBD>s<EFBFBD>Q CREATE TABLE `<60>s<EFBFBD>Q` (
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
`<60>b<EFBFBD>Q` char(1) NOT NULL,
`<60>b<EFBFBD>P` enum('<27><>','<27><>','<27><>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>R`;
Table Create Table
<EFBFBD>s<EFBFBD>R CREATE TABLE `<60>s<EFBFBD>R` (
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
`<60>b<EFBFBD>Q` char(1) NOT NULL,
`<60>b<EFBFBD>P` enum('<27>\','<27>\','<27>\') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>S`;
Table Create Table
<EFBFBD>s<EFBFBD>S CREATE TABLE `<60>s<EFBFBD>S` (
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
`<60>b<EFBFBD>Q` char(1) NOT NULL,
`<60>b<EFBFBD>P` enum('<27>','<27>','<27>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>T`;
Table Create Table
<EFBFBD>s<EFBFBD>T CREATE TABLE `<60>s<EFBFBD>T` (
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
`<60>b<EFBFBD>Q` char(1) NOT NULL,
`<60>b<EFBFBD>P` enum('<27><>','<27><>','<27><>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>U`;
Table Create Table
<EFBFBD>s<EFBFBD>U CREATE TABLE `<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
`<60>b<EFBFBD>Q` char(1) NOT NULL,
`<60>b<EFBFBD>P` enum('<27>\','<27>\','<27>\') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>s<EFBFBD>V`;
Table Create Table
<EFBFBD>s<EFBFBD>V CREATE TABLE `<60>s<EFBFBD>V` (
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
`<60>b<EFBFBD>Q` char(1) NOT NULL,
`<60>b<EFBFBD>P` enum('<27>','<27>','<27>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
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
) ENGINE=MEMORY DEFAULT CHARSET=sjis
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
SHOW CREATE TABLE `<60>s<EFBFBD>W`;
Table Create Table
<EFBFBD>s<EFBFBD>W CREATE TABLE `<60>s<EFBFBD>W` (
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
`<60>b<EFBFBD>Q` char(1) NOT NULL,
`<60>b<EFBFBD>P` enum('<27><>','<27><>','<27><>') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
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
) ENGINE=MEMORY DEFAULT CHARSET=sjis
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
SHOW CREATE TABLE `<60>s<EFBFBD>X`;
Table Create Table
<EFBFBD>s<EFBFBD>X CREATE TABLE `<60>s<EFBFBD>X` (
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
`<60>b<EFBFBD>Q` char(1) NOT NULL,
`<60>b<EFBFBD>P` enum('<27>\','<27>\','<27>\') DEFAULT NULL,
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
KEY `<60>b<EFBFBD>P` (`<60>b<EFBFBD>P`)
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
) ENGINE=MEMORY DEFAULT CHARSET=sjis
CREATE TABLE t1(c1 enum('<27>S','<27>s')) default character set = sjis;
INSERT INTO t1 VALUES('<27>S'),('<27>s');
SELECT * FROM t1 WHERE c1 LIKE '<27>S';
c1
<EFBFBD>S
DROP TABLE t1;
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
DESC `<60>s<EFBFBD>P`;
Field Type Null Key Default Extra
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
<EFBFBD>b<EFBFBD>Q char(1) NO NULL
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
<EFBFBD>b<EFBFBD>P enum('<27>','<27>','<27>') YES MUL NULL
DESC `<60>s<EFBFBD>Q`;
Field Type Null Key Default Extra
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
<EFBFBD>b<EFBFBD>Q char(1) NO NULL
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
<EFBFBD>b<EFBFBD>P enum('<27><>','<27><>','<27><>') YES MUL NULL
DESC `<60>s<EFBFBD>R`;
Field Type Null Key Default Extra
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
<EFBFBD>b<EFBFBD>Q char(1) NO NULL
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
<EFBFBD>b<EFBFBD>P enum('<27>\','<27>\','<27>\') YES MUL NULL
DESC `<60>s<EFBFBD>S`;
Field Type Null Key Default Extra
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
<EFBFBD>b<EFBFBD>Q char(1) NO NULL
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
<EFBFBD>b<EFBFBD>P enum('<27>','<27>','<27>') YES MUL NULL
DESC `<60>s<EFBFBD>T`;
Field Type Null Key Default Extra
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
<EFBFBD>b<EFBFBD>Q char(1) NO NULL
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
<EFBFBD>b<EFBFBD>P enum('<27><>','<27><>','<27><>') YES MUL NULL
DESC `<60>s<EFBFBD>U`;
Field Type Null Key Default Extra
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
<EFBFBD>b<EFBFBD>Q char(1) NO NULL
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
<EFBFBD>b<EFBFBD>P enum('<27>\','<27>\','<27>\') YES MUL NULL
DESC `<60>s<EFBFBD>V`;
Field Type Null Key Default Extra
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
<EFBFBD>b<EFBFBD>Q char(1) NO NULL
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
<EFBFBD>b<EFBFBD>P enum('<27>','<27>','<27>') YES MUL NULL
DESC `<60>s<EFBFBD>W`;
Field Type Null Key Default Extra
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
<EFBFBD>b<EFBFBD>Q char(1) NO NULL
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
<EFBFBD>b<EFBFBD>P enum('<27><>','<27><>','<27><>') YES MUL NULL
DESC `<60>s<EFBFBD>X`;
Field Type Null Key Default Extra
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
<EFBFBD>b<EFBFBD>Q char(1) NO NULL
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
<EFBFBD>b<EFBFBD>P enum('<27>\','<27>\','<27>\') YES MUL NULL
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