mirror of
https://github.com/MariaDB/server.git
synced 2025-01-18 04:53:01 +01:00
f4ff086abe
PROBLEMS Description:- Server variable "--lower_case_tables_names" when set to "0" on windows platform which does not support case sensitive file operations leads to problems. A warning message is printed in the error log while starting the server with "--lower_case_tables_names=0". Also according to the documentation, seting "lower_case_tables_names" to "0" on a case-insensitive filesystem might lead to index corruption. Analysis:- The problem reported in the bug is:- Creating an INNODB table 'a' and executing a query, "INSERT INTO a SELECT a FROM A;" on a server started with "--lower_case_tables_names=0" and running on a case-insensitive filesystem leads innodb to flat spin. Optimizer thinks that "a" and "A" are two different tables as the variable "lower_case_table_names" is set to "0". As a result, optimizer comes up with a plan which does not need a temporary table. If the same table is used in select and insert, a temporary table is needed. This incorrect optimizer plan leads to infinite insertions. Fix:- If the server is started with "--lower_case_tables_names" set to 0 on a case-insensitive filesystem, an error, "The server option 'lower_case_table_names'is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.", is printed in the server error log and the server exits.
130 lines
3.9 KiB
Text
130 lines
3.9 KiB
Text
#Server variable option 'lower_case_table_names' sets '0' as default value
|
||
#in case sensitive filesystem. Using 'lower_case_table_names=0' in case of
|
||
#insensitive filsystem is not allowed.
|
||
-- source include/have_case_sensitive_file_system.inc
|
||
--source include/have_sjis.inc
|
||
--source include/have_innodb.inc
|
||
--character_set sjis
|
||
--disable_warnings
|
||
drop table if exists `Ｔ１`;
|
||
drop table if exists `Ｔ２`;
|
||
drop table if exists `Ｔ３`;
|
||
drop table if exists `Ｔ４`;
|
||
drop table if exists `Ｔ５`;
|
||
drop table if exists `Ｔ６`;
|
||
drop table if exists `Ｔ７`;
|
||
drop table if exists `Ｔ８`;
|
||
drop table if exists `Ｔ９`;
|
||
drop table if exists t1;
|
||
--enable_warnings
|
||
|
||
#
|
||
# Test ENUM values with Japanese characters in sjis encoding
|
||
#
|
||
|
||
SET NAMES sjis;
|
||
SET character_set_database = sjis;
|
||
|
||
CREATE TABLE `Ｔ１` (`Ｃ１` ENUM('ｱ','ｲ','ｳ'), INDEX(`Ｃ１`)) DEFAULT CHARSET = sjis engine = innodb;
|
||
CREATE TABLE `Ｔ２` (`Ｃ１` ENUM('あ','い','う'), INDEX(`Ｃ１`)) DEFAULT CHARSET = sjis engine = innodb;
|
||
CREATE TABLE `Ｔ３` (`Ｃ１` ENUM('ソ','十','表'), INDEX(`Ｃ１`)) DEFAULT CHARSET = sjis engine = innodb;
|
||
CREATE TABLE `Ｔ４` (`Ｃ１` ENUM('ｱ','ｲ','ｳ'), INDEX(`Ｃ１`)) DEFAULT CHARSET = sjis engine = myisam;
|
||
CREATE TABLE `Ｔ５` (`Ｃ１` ENUM('あ','い','う'), INDEX(`Ｃ１`)) DEFAULT CHARSET = sjis engine = myisam;
|
||
CREATE TABLE `Ｔ６` (`Ｃ１` ENUM('ソ','十','表'), INDEX(`Ｃ１`)) DEFAULT CHARSET = sjis engine = myisam;
|
||
CREATE TABLE `Ｔ７` (`Ｃ１` ENUM('ｱ','ｲ','ｳ'), INDEX(`Ｃ１`)) DEFAULT CHARSET = sjis engine = MEMORY;
|
||
CREATE TABLE `Ｔ８` (`Ｃ１` ENUM('あ','い','う'), INDEX(`Ｃ１`)) DEFAULT CHARSET = sjis engine = MEMORY;
|
||
CREATE TABLE `Ｔ９` (`Ｃ１` ENUM('ソ','十','表'), INDEX(`Ｃ１`)) DEFAULT CHARSET = sjis engine = MEMORY;
|
||
|
||
INSERT INTO `Ｔ１` VALUES ('ｱ'),('ｲ'),('ｳ');
|
||
INSERT INTO `Ｔ２` VALUES ('あ'),('い'),('う');
|
||
INSERT INTO `Ｔ３` VALUES ('ソ'),('十'),('表');
|
||
INSERT INTO `Ｔ４` VALUES ('ｱ'),('ｲ'),('ｳ');
|
||
INSERT INTO `Ｔ５` VALUES ('あ'),('い'),('う');
|
||
INSERT INTO `Ｔ６` VALUES ('ソ'),('十'),('表');
|
||
INSERT INTO `Ｔ７` VALUES ('ｱ'),('ｲ'),('ｳ');
|
||
INSERT INTO `Ｔ８` VALUES ('あ'),('い'),('う');
|
||
INSERT INTO `Ｔ９` VALUES ('ソ'),('十'),('表');
|
||
|
||
SELECT * FROM `Ｔ１`;
|
||
SELECT * FROM `Ｔ２`;
|
||
SELECT * FROM `Ｔ３`;
|
||
SELECT * FROM `Ｔ４`;
|
||
SELECT * FROM `Ｔ５`;
|
||
SELECT * FROM `Ｔ６`;
|
||
SELECT * FROM `Ｔ７`;
|
||
SELECT * FROM `Ｔ８`;
|
||
SELECT * FROM `Ｔ９`;
|
||
|
||
SHOW CREATE TABLE `Ｔ１`;
|
||
SHOW CREATE TABLE `Ｔ２`;
|
||
SHOW CREATE TABLE `Ｔ３`;
|
||
SHOW CREATE TABLE `Ｔ４`;
|
||
SHOW CREATE TABLE `Ｔ５`;
|
||
SHOW CREATE TABLE `Ｔ６`;
|
||
SHOW CREATE TABLE `Ｔ７`;
|
||
SHOW CREATE TABLE `Ｔ８`;
|
||
SHOW CREATE TABLE `Ｔ９`;
|
||
|
||
DESC `Ｔ１`;
|
||
DESC `Ｔ２`;
|
||
DESC `Ｔ３`;
|
||
DESC `Ｔ４`;
|
||
DESC `Ｔ５`;
|
||
DESC `Ｔ６`;
|
||
DESC `Ｔ７`;
|
||
DESC `Ｔ８`;
|
||
DESC `Ｔ９`;
|
||
|
||
#
|
||
# Test problem with enum values after the colum with NOT NULL restriction
|
||
#
|
||
|
||
ALTER TABLE `Ｔ１` ADD `Ｃ２` CHAR(1) NOT NULL FIRST;
|
||
ALTER TABLE `Ｔ２` ADD `Ｃ２` CHAR(1) NOT NULL FIRST;
|
||
ALTER TABLE `Ｔ３` ADD `Ｃ２` CHAR(1) NOT NULL FIRST;
|
||
ALTER TABLE `Ｔ４` ADD `Ｃ２` CHAR(1) NOT NULL FIRST;
|
||
ALTER TABLE `Ｔ５` ADD `Ｃ２` CHAR(1) NOT NULL FIRST;
|
||
ALTER TABLE `Ｔ６` ADD `Ｃ２` CHAR(1) NOT NULL FIRST;
|
||
ALTER TABLE `Ｔ７` ADD `Ｃ２` CHAR(1) NOT NULL FIRST;
|
||
ALTER TABLE `Ｔ８` ADD `Ｃ２` CHAR(1) NOT NULL FIRST;
|
||
ALTER TABLE `Ｔ９` ADD `Ｃ２` CHAR(1) NOT NULL FIRST;
|
||
|
||
SHOW CREATE TABLE `Ｔ１`;
|
||
SHOW CREATE TABLE `Ｔ２`;
|
||
SHOW CREATE TABLE `Ｔ３`;
|
||
SHOW CREATE TABLE `Ｔ４`;
|
||
SHOW CREATE TABLE `Ｔ５`;
|
||
SHOW CREATE TABLE `Ｔ６`;
|
||
SHOW CREATE TABLE `Ｔ７`;
|
||
SHOW CREATE TABLE `Ｔ８`;
|
||
SHOW CREATE TABLE `Ｔ９`;
|
||
|
||
#
|
||
# Test to distinguish 0x9353 and 0x9373
|
||
# Bug#6206 ENUMs are not case sensitive even if declared BINARY
|
||
#
|
||
|
||
CREATE TABLE t1(c1 enum('鉄','都')) default character set = sjis;
|
||
INSERT INTO t1 VALUES('鉄'),('都');
|
||
SELECT * FROM t1 WHERE c1 LIKE '鉄';
|
||
DROP TABLE t1;
|
||
|
||
DESC `Ｔ１`;
|
||
DESC `Ｔ２`;
|
||
DESC `Ｔ３`;
|
||
DESC `Ｔ４`;
|
||
DESC `Ｔ５`;
|
||
DESC `Ｔ６`;
|
||
DESC `Ｔ７`;
|
||
DESC `Ｔ８`;
|
||
DESC `Ｔ９`;
|
||
|
||
DROP TABLE `Ｔ１`;
|
||
DROP TABLE `Ｔ２`;
|
||
DROP TABLE `Ｔ３`;
|
||
DROP TABLE `Ｔ４`;
|
||
DROP TABLE `Ｔ５`;
|
||
DROP TABLE `Ｔ６`;
|
||
DROP TABLE `Ｔ７`;
|
||
DROP TABLE `Ｔ８`;
|
||
DROP TABLE `Ｔ９`;
|