ThisOnly opened a new issue, #26724:
URL: https://github.com/apache/shardingsphere/issues/26724

   ## Bug Report
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ShardingSphere did you use?
   5.3.2
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy
   
   ### Expected behavior
   The following is my configuration and executed SQL
   
   
![image](https://github.com/apache/shardingsphere/assets/41990755/06b43e14-0a1e-495a-93ed-f5eed3507d69)
   
   
![image](https://github.com/apache/shardingsphere/assets/41990755/b67f350f-184c-4a07-9ce3-5e6ec6557543)
   
   The executed SQL carries sub database and sub table fields, partion_value is 
1, theoretically speaking, SQL will only be used in ds_ 1 library execution, 
but in reality ds_ 0 has also been executed
   
   The actual executed SQL is as follows
   
![1688184467641](https://github.com/apache/shardingsphere/assets/41990755/6abd1d72-cf3e-493b-9da3-609bea12f16c)
   
   
   
   ### Actual behavior
   This SQL should not be in ds_0 Execute 
   
   ### Reason analyze (If you can)
   This SQL carries a table partitioning key,and the sub database key is in the 
sub query
   
   ### 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).
   


-- 
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]

Reply via email to