summaryrefslogtreecommitdiff
path: root/mysql-test/r/lowercase_table3.result
Commit message (Collapse)AuthorAgeFilesLines
* Bug#20198490 : LOWER_CASE_TABLE_NAMES=0 ON WINDOWS LEADS TOArun Kuruvila2015-08-211-11/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Bug #42408 Faulty regex for detecting [Warning] and [ERROR] in mysqld error logBjorn Munch2009-08-281-1/+1
| | | | Some follow-up test fixes after seeing effect in PB2
* BUG#32667: lowercase_table3.test reports to error logPatrick Crews2009-02-131-8/+8
| | | | | Cleaned up SQL code in the test. Needed to move the FLUSH TABLES statement prior to the DROP TABLE t1 to prevent a warning of Table open on delete and a test fail.
* BUG#39853: lowercase_table3 fails on powermacg5 in rpl treeSven Sandberg2008-11-141-0/+1
| | | | post-push fix. forgot to update result file.
* BUG#29839 - lowercase_table3.test: Cannot find table test/T1 fromsvoj@mysql.com/june.mysql.com2007-07-181-4/+4
| | | | | | | the internal data dictiona - re-enabled lowercase_table3 test; - added a rule to throw away expected warning to mtr_report.pl; - fixed a test case to produce unique warning.
* Fix for bug#8156:information_schema and lowercase_table3 fail on OSXgluh@gluh.mysql.r18.ru2005-02-141-1/+1
| | | | | Can't repeat information_schema test failure Fix for lowercase_table3 only
* lowercase_table3.result:heikki@hundin.mysql.fi2004-11-251-1/+1
| | | | Correct InnoDB's result output in test; the pseudo-file-extension for InnoDB tables '.InnoDB' was replaced by a more realistic '.ibd' extension
* after merge fixserg@serg.mylan2004-06-281-1/+1
|
* after merge fixserg@serg.mylan2004-06-271-2/+2
|
* Fixed memory leak in DROP DATABASE when using RAID tables (Bug #2882)monty@mysql.com2004-03-101-1/+1
|
* Ensure that one can't from the command line set a variable too small. (Bug ↵monty@mysql.com2004-03-061-0/+10
#2710) Allow one to force lower_case_table_names to 0, even if the file system is case insensitive. This fixes some issues on Mac OS X (Bug #2994) Added variables "lower_case_file_system", "version_compile_os" and "license"