mysql - 逆向工程，将我的脚本导入 mysql workbench 后没有任何关系

Question

出于某种原因，我无法再打开我的模型，它已损坏，所以我尝试从 MySQL 导入以创建一个新模型进行操作，但在导入时总是出现此错误:

WARNING: Table `macrotelecom_django`.`perfil` not found. Stub was created.
WARNING: Table `macrotelecom_django`.`Agentes` : Foreign key `fk_Agentes_Perfil1` :     Referred column `macrotelecom_django`.`perfil`.`idPerfil` not found. Stub was created.
WARNING: Table `macrotelecom_django`.`usuariologin` not found. Stub was created.
WARNING: Table `macrotelecom_django`.`Agentes` : Foreign key `fk_Agentes_UsuarioLogin1` :   Referred column `macrotelecom_django`.`usuariologin`.`idUsuarioLogin` not found. Stub was created.
WARNING: Table `macrotelecom_django`.`clientes` not found. Stub was created.
WARNING: Table `macrotelecom_django`.`Albaran` : Foreign key `fk_Clientes_has_Productos_Clientes1` : Referred column `macrotelecom_django`.`clientes`.`idCliente` not found. Stub was created. 
WARNING: Table `macrotelecom_django`.`productos` not found. Stub was created.
WARNING: Table `macrotelecom_django`.`Albaran` : Foreign key `fk_Clientes_has_Productos_Productos1` : Referred column 
...

由于某些原因，它无法正确导入外键，当创建总是在约束之前实现时总是说“找不到表”，这可能是什么？

Answer 1

如 MySQL 错误报告 here 中所述，这应该是一个区分大小写的问题.

Potentially Workbench could check for lower_case_table_names variable value before starting reverse-engineering and adopt SqlIdentifiersCS as needed, but that migh lead to undesirable mix of casing in the model. For example several schemata were reverse-engineered from different DBMS that use different value for lower_case_table_names. So user has to explicitly set SqlIdentifiersCS parameter in Workbench and apply same rule set every time.