lower_case_table_names引數設定解決Error Code: 1146. Table doesn't exist?

在 MariaDB 10.2.11 for windows中使用mysqldump匯出DB，並匯入Mysql 5.7.16 for Linux後，在程式執行時報錯：Error Code: 1146. Table XXX doesn't exist

檢查程式程式碼發現執行SQL :SELECT * FROM Base_User ... 報的錯，但檢查Mysql 5.7.16 for Linux 中table卻存在。
嘗試把SQL中駝峰式表名(Base_User)改為全小寫表名SELECT * FROM base_user可以正常執行，原來是因為Mysql for Linux中預設大小敏感，而windows中預設大小寫不敏感。

在my.cnf設定引數 lower_case_table_names 為1，並重啟mysql後大小寫不敏感

[mysqld]
lower_case_table_names=1

參考文件：
lower_case_table_names

If set to 0, table names are stored as specified and comparisons are case-sensitive. 
If set to 1, table names are stored in lowercase on disk and comparisons are not case sensitive. 
If set to 2, table names are stored as given but compared in lowercase. This option also applies to database names and table aliases. 

On Windows the default value is 1. On OS X, the default value is 2.

You should not set lower_case_table_names to 0 if you are running MySQL on a system where the data directory resides on a case-insensitive file system (such as on Windows or OS X). 
It is an unsupported combination that could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_nameoperation with the wrong tbl_name letter case. With MyISAM, accessing table names using different letter cases could cause index corruption.

As of MySQL 5.7.9, an error message is printed and the server exits if you attempt to start the server with --lower_case_table_names=0 on a case-insensitive file system.

If you are using InnoDB tables, you should set this variable to 1 on all platforms to force names to be converted to lowercase.

The setting of this variable in MySQL 5.7 affects the behavior of replication filtering options with regard to case sensitivity.