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_db_ujis.result

23 lines
456 B
Text
Raw Normal View History

Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
drop database if exists `<60>ƎΎݎ<CE8E><DD8E><EFBFBD>`;
drop database if exists `<60><><EFBFBD>ܸ<EFBFBD>`;
drop database if exists `<60><>܏<EFBFBD>ݏ<EFBFBD><DD8F>`;
SET NAMES ujis;
SET character_set_database = ujis;
CREATE DATABASE `<60>ƎΎݎ<CE8E><DD8E><EFBFBD>`;
CREATE DATABASE `<60><><EFBFBD>ܸ<EFBFBD>`;
CREATE DATABASE `<60><>܏<EFBFBD>ݏ<EFBFBD><DD8F>`;
SHOW DATABASES;
Database
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
information_schema
Added test data, test case and test result files for Japanese characters test. I have put the tests into a separate "suite", the first one actually. Currently this can only be run by the Perl version of mysql-test-run that is not quite finished. It should, or at least will, be able to be run with the line ./mysql-test-run.pl --suite=jp
2005-01-07 00:48:38 -08:00
<EFBFBD><EFBFBD><EFBFBD>ܸ<EFBFBD>
<EFBFBD><EFBFBD>܏<EFBFBD>ݏ<EFBFBD><EFBFBD>
<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
mysql
test
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
USE `<60>ƎΎݎ<CE8E><DD8E><EFBFBD>`;
USE `<60><><EFBFBD>ܸ<EFBFBD>`;
USE `<60><>܏<EFBFBD>ݏ<EFBFBD><DD8F>`;
DROP DATABASE `<60>ƎΎݎ<CE8E><DD8E><EFBFBD>`;
DROP DATABASE `<60><><EFBFBD>ܸ<EFBFBD>`;
DROP DATABASE `<60><>܏<EFBFBD>ݏ<EFBFBD><DD8F>`;
Reference in a new issue Copy permalink