Closed strongduanmu closed 2 years ago
I found that this is a bug caused by ShardingSphereMetaData, when we create uppercase database name and schema name, ShardingSphereMetaData cannot support case-insensitive configuration. We need to avoid using the schemas fields of ShardingSphereDatabase and databases field of ShardingSphereMetaData directly.
Bug Report
Which version of ShardingSphere did you use?
https://github.com/apache/shardingsphere/commit/cb3cbe99d8bb41d25e55f4bd404ecf7e5cfeb287
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
Expected behavior
Execute show tables statement successfully.
Actual behavior
Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Example codes for reproduce this issue (such as a github link).