linux1146错误,lower_case_table_names参数设置解决Error Code: 1146. Table doesn't exist?

在MariaDB 10.2.11forwindows中使用mysqldump导出DB，并导入Mysql5.7.16for Linux后，在程式执行时报错：Error Code: 1146. Table XXXdoesn't exist

检查程式代码发现执行SQL :SELECT * FROMBase_User... 报的错，但检查Mysql5.7.16for Linux中table却存在。

尝试把SQL中驼峰式表名(Base_User)改为全小写表名SELECT * FROMbase_user可以正常执行，原来是因为Mysql forLinux中默认大小敏感，而windows中默认大小写不敏感。

在my.cnf设置参数lower_case_table_names 为1，并重启mysql后大小写不敏感

Property

Value

Command-Line Format

--lower-case-table-names[=#]

Scope

Global

Dynamic

No

Type

integer

Default

0

Minimum

0

Maximum

2

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.

本文来自互联网用户投稿，文章观点仅代表作者本人，不代表本站立场，不承担相关法律责任。如若转载，请注明出处。 如若内容造成侵权/违法违规/事实不符，请点击【内容举报】进行投诉反馈！