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

   ### Which version of ShardingSphere did you use?
   ShardingSphere-5.2.0
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-JDBC
   ### Expected behavior
   执行SQL
   ```SQL
   select * from f_busi where start_time > "2022-11-01 00:00:00" and start_time 
< "2024-03-01 00:00:00"
   ```
   The result seems to be generated according to Cartesian product
   ```
   routeDataSources:[fbusi-2024, fbusi-2022, fbusi-2023]
   ```
   ```
   routeTables:
   [f_busi_06, f_busi_05, f_busi_04, f_busi_03, f_busi_09, f_busi_08, 
f_busi_07, f_busi_02, f_busi_12, f_busi_01, f_busi_11, f_busi_10]
   [f_busi_06, f_busi_05, f_busi_04, f_busi_03, f_busi_09, f_busi_08, 
f_busi_07, f_busi_02, f_busi_12, f_busi_01, f_busi_11, f_busi_10]
   [f_busi_06, f_busi_05, f_busi_04, f_busi_03, f_busi_09, f_busi_08, 
f_busi_07, f_busi_02, f_busi_12, f_busi_01, f_busi_11, f_busi_10]
   ```
   ### Actual behavior
   ```
   routeDataSources:[fbusi-2024, fbusi-2022, fbusi-2023]
   ```
   ```
   routeTables:
   [f_busi_11, f_busi_12]
   [f_busi_06, f_busi_05, f_busi_04, f_busi_03, f_busi_09, f_busi_08, 
f_busi_07, f_busi_02, f_busi_12, f_busi_01, f_busi_11, f_busi_10]
   f_busi_03,f_busi_02, f_busi_01]
   ```
   ### Reason analyze (If you can)
   The data source information cannot be obtained in the implementation of this 
interface
   
![image](https://user-images.githubusercontent.com/74887513/225547846-b21bdf59-dcd3-48ce-8116-964abe1b9183.png)
   Because the data source information in the source code is not transferred
   
![image](https://user-images.githubusercontent.com/74887513/225548271-0008e8f7-6a32-4fc7-817c-5e8684a1d422.png)
   
   


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