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/r/jp_create_tbl_sjis.result

522 lines
17 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
SET NAMES sjis;
SET character_set_database = sjis;
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><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE IF EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE IF EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE IF EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE IF EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE IF EXISTS `<60>\<5C>\<5C>\`;
DROP TABLE IF EXISTS `<60>\<5C>\<5C>\`;
DROP TABLE IF EXISTS `<60>\<5C>\<5C>\`;
DROP TABLE IF EXISTS `<60>\<5C>\<5C>\`;
DROP TABLE IF EXISTS `<60>\<5C>\<5C>\`;
CREATE TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = ujis engine=INNODB;
CREATE TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = ujis engine=INNODB;
CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
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
Warnings:
Note 1050 Table '<27><><EFBFBD>' already exists
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
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
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
Warnings:
Note 1050 Table '<27><><EFBFBD>' already exists
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
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
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
Warnings:
Note 1050 Table '<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>' already exists
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
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
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
Warnings:
Note 1050 Table '<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>' already exists
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
CREATE TABLE IF NOT EXISTS `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
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
Warnings:
Note 1050 Table '<27>\<5C>\<5C>\' already exists
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
CREATE TABLE IF NOT EXISTS `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
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
Warnings:
Note 1050 Table '<27>\<5C>\<5C>\' already exists
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
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TABLE IF NOT EXISTS `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\`char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TEMPORARY TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TEMPORARY TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=INNODB;
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=ujis
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=ujis
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=InnoDB DEFAULT CHARSET=sjis
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
CREATE TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) 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
Warnings:
Note 1050 Table '<27><><EFBFBD>' already exists
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
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) 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
Warnings:
Note 1050 Table '<27><><EFBFBD>' already exists
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
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) 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
Warnings:
Note 1050 Table '<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>' already exists
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
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) 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
Warnings:
Note 1050 Table '<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>' already exists
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
CREATE TABLE IF NOT EXISTS `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) 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
Warnings:
Note 1050 Table '<27>\<5C>\<5C>\' already exists
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
CREATE TABLE IF NOT EXISTS `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) 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
Warnings:
Note 1050 Table '<27>\<5C>\<5C>\' already exists
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
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TABLE IF NOT EXISTS `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\`char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TEMPORARY TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TEMPORARY TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=MyISAM;
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<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
`<60><><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
SHOW CREATE TABLE `<60>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) 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
) ENGINE=MyISAM DEFAULT CHARSET=sjis
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
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(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
Warnings:
Note 1050 Table '<27><><EFBFBD>' already exists
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
Warnings:
Note 1050 Table '<27><><EFBFBD>' already exists
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
Warnings:
Note 1050 Table '<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>' already exists
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
Warnings:
Note 1050 Table '<27><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>' already exists
CREATE TABLE IF NOT EXISTS `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
Warnings:
Note 1050 Table '<27>\<5C>\<5C>\' already exists
CREATE TABLE IF NOT EXISTS `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
Warnings:
Note 1050 Table '<27>\<5C>\<5C>\' already exists
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TABLE IF NOT EXISTS `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TABLE IF NOT EXISTS `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\`char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TEMPORARY TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TEMPORARY TABLE `<60><><EFBFBD>`(`<60><><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`(`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) DEFAULT CHARSET = sjis engine=MEMORY;
CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\`(`<60>\<5C>\<5C>\` char(1)) 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
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Field Type Null Key Default Extra
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
DESC `<60>\<5C>\<5C>\`;
Field Type Null Key Default Extra
<EFBFBD>\<5C>\<5C>\ char(1) YES NULL
SHOW CREATE TABLE `<60><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<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
`<60><><EFBFBD>` char(1) DEFAULT NULL
) 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><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<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
`<60><><EFBFBD>` char(1) DEFAULT NULL
) 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><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<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
`<60><><EFBFBD>` char(1) DEFAULT NULL
) 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><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<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
`<60><><EFBFBD>` char(1) DEFAULT NULL
) 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><><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<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
`<60><><EFBFBD>` char(1) DEFAULT NULL
) 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><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) DEFAULT NULL
) 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><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) DEFAULT NULL
) 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><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) DEFAULT NULL
) 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><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) DEFAULT NULL
) 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><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
Table Create Table
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> CREATE TEMPORARY TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><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
`<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` char(1) DEFAULT NULL
) 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>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) DEFAULT NULL
) 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>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) DEFAULT NULL
) 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>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) DEFAULT NULL
) 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>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) DEFAULT NULL
) 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>\<5C>\<5C>\`;
Table Create Table
<EFBFBD>\<5C>\<5C>\ CREATE TEMPORARY TABLE `<60>\<5C>\<5C>\` (
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>\<5C>\<5C>\` char(1) DEFAULT NULL
) 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
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
DROP TABLE `<60>\<5C>\<5C>\`;
Reference in a new issue Copy permalink