yflytom opened a new issue, #30005: URL: https://github.com/apache/shardingsphere/issues/30005
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? shardingjdbc 5.4.1 ### Expected behavior When querying connected tables, the size is ignored and the custom algorithm can be entered normally. 连表查询时大小忽略可以正常进入自定义算法中 ### Actual behavior Capital letters cannot enter the custom sharding algorithm when querying connected tables. 连表查询时大写无法进入自定义分片算法中 ### Reason analyze (If you can) When querying a single table, uppercase letters can enter the custom sharding algorithm, but not after joining the tables. Is the case problem not ignored after joining the tables? My ability is limited and I haven’t checked the source code yet. Sorry. 单表查询时大写可以进入自定义分片算法，但是连表后就不行，是否连表后未忽略大小写问题，能力有限对源码还未查看，见谅 ### 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). https://github.com/yflytom/sharding-bug-demo-master.git -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
