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

444 lines
9.4 KiB
Text
Raw Normal View History

Fix for Bug#28563 Test suite "jp" fails completely - The main goal of this fix is to make the "jp" suite runnable in general and to make it more robust for use in pushbuild under build team conditions. - It was decided to fix the remaining heavy issues within the architecture of this test later (-> WL 4327 Redesign the 'jp' testsuite for build team testing conditions) Only the test jp_trim_sjis got some significant improvements of its architecture (Just as proof of concept for the other tests). - Tests suffering from Bug 36597 Testsuite "jp": Suspicious results for some tests (unexpected result sets) were disabled - *.opt files were used to avoid differences on OS (Windows) because of case sensitive tablenames within the tests
2008-05-15 18:01:13 +02:00
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>a`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>b`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>a`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>b`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>a`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>b`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>a`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>b`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>a`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>b`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>a`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>b`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>a`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>b`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>a`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>b`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>a`;
DROP TABLE IF EXISTS `<60>ԣ<EFBFBD>b`;
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 ujis;
SET character_set_database = ujis;
CREATE TABLE `<60>ԣ<EFBFBD>a` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>b` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>a` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>b` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>a` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = innodb;
CREATE TABLE `<60>ԣ<EFBFBD>b` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis 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
CREATE TABLE `<60>ԣ<EFBFBD>a` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>b` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>a` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>b` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>a` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>b` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = myisam;
CREATE TABLE `<60>ԣ<EFBFBD>a` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = memory;
CREATE TABLE `<60>ԣ<EFBFBD>b` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = memory;
CREATE TABLE `<60>ԣ<EFBFBD>a` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = memory;
CREATE TABLE `<60>ԣ<EFBFBD>b` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = memory;
CREATE TABLE `<60>ԣ<EFBFBD>a` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = memory;
CREATE TABLE `<60>ԣ<EFBFBD>b` (`<60>ã<EFBFBD>` char(1) PRIMARY KEY) DEFAULT CHARSET = ujis engine = memory;
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
INSERT INTO `<60>ԣ<EFBFBD>a` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>b` VALUES ('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>a` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>b` VALUES ('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>a` VALUES ('<27><><EFBFBD>'),('<27><><EFBFBD>'),('<27><><EFBFBD>');
INSERT INTO `<60>ԣ<EFBFBD>b` VALUES ('<27><><EFBFBD>');
INSERT INTO `<60>ԣ<EFBFBD>a` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>b` VALUES ('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>a` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>b` VALUES ('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>a` VALUES ('<27><><EFBFBD>'),('<27><><EFBFBD>'),('<27><><EFBFBD>');
INSERT INTO `<60>ԣ<EFBFBD>b` VALUES ('<27><><EFBFBD>');
INSERT INTO `<60>ԣ<EFBFBD>a` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>b` VALUES ('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>a` VALUES ('<27><>'),('<27><>'),('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>b` VALUES ('<27><>');
INSERT INTO `<60>ԣ<EFBFBD>a` VALUES ('<27><><EFBFBD>'),('<27><><EFBFBD>'),('<27><><EFBFBD>');
INSERT INTO `<60>ԣ<EFBFBD>b` VALUES ('<27><><EFBFBD>');
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` CROSS JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> NULL
<EFBFBD><EFBFBD> NULL
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
NULL <09><>
NULL <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` CROSS JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> NULL
<EFBFBD><EFBFBD> NULL
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
NULL <09><>
NULL <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` CROSS JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> NULL
<EFBFBD><EFBFBD><EFBFBD> NULL
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
NULL <09><><EFBFBD>
NULL <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` CROSS JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> NULL
<EFBFBD><EFBFBD> NULL
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
NULL <09><>
NULL <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` CROSS JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> NULL
<EFBFBD><EFBFBD> NULL
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
NULL <09><>
NULL <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` CROSS JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> NULL
<EFBFBD><EFBFBD><EFBFBD> NULL
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
NULL <09><><EFBFBD>
NULL <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` CROSS JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> NULL
<EFBFBD><EFBFBD> NULL
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
NULL <09><>
NULL <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` CROSS JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
<EFBFBD><EFBFBD> NULL
<EFBFBD><EFBFBD> NULL
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
<EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD> <09><>
NULL <09><>
NULL <09><>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` INNER JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` CROSS JOIN `<60>ԣ<EFBFBD>b`;
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>a` LEFT JOIN `<60>ԣ<EFBFBD>b` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> NULL
<EFBFBD><EFBFBD><EFBFBD> NULL
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` USING (`<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
<EFBFBD>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
<EFBFBD><EFBFBD><EFBFBD>
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
SELECT * FROM `<60>ԣ<EFBFBD>b` RIGHT JOIN `<60>ԣ<EFBFBD>a` ON (`<60>ԣ<EFBFBD>a`.`<60>ã<EFBFBD>` = `<60>ԣ<EFBFBD>b`.`<60>ã<EFBFBD>`);
<EFBFBD>ã<EFBFBD> <09>ã<EFBFBD>
<EFBFBD><EFBFBD><EFBFBD> <09><><EFBFBD>
NULL <09><><EFBFBD>
NULL <09><><EFBFBD>
DROP TABLE `<60>ԣ<EFBFBD>a`;
DROP TABLE `<60>ԣ<EFBFBD>b`;
DROP TABLE `<60>ԣ<EFBFBD>a`;
DROP TABLE `<60>ԣ<EFBFBD>b`;
DROP TABLE `<60>ԣ<EFBFBD>a`;
DROP TABLE `<60>ԣ<EFBFBD>b`;
DROP TABLE `<60>ԣ<EFBFBD>a`;
DROP TABLE `<60>ԣ<EFBFBD>b`;
DROP TABLE `<60>ԣ<EFBFBD>a`;
DROP TABLE `<60>ԣ<EFBFBD>b`;
DROP TABLE `<60>ԣ<EFBFBD>a`;
DROP TABLE `<60>ԣ<EFBFBD>b`;
DROP TABLE `<60>ԣ<EFBFBD>a`;
DROP TABLE `<60>ԣ<EFBFBD>b`;
DROP TABLE `<60>ԣ<EFBFBD>a`;
DROP TABLE `<60>ԣ<EFBFBD>b`;
DROP TABLE `<60>ԣ<EFBFBD>a`;
DROP TABLE `<60>ԣ<EFBFBD>b`;
Reference in a new issue Copy permalink