huangpang opened a new issue #8378: URL: https://github.com/apache/shardingsphere/issues/8378
## Bug Report I upgraded from 4.0.0-rc1 to 4.1.1 After upgrading to 4.1.1, it is found that the normal business function (paging query) cannot be used Because we operate on mybatis-plus, we will count first and then perform paging query Observe the log, and find that count has normal table splitting The SQL statement is: select count (*) from t_ Xx_ 202011 hundred and two thousand and eleven However, when querying data, there is no correct sub table, or the previous table is queried, resulting in the data can not be found out After continuous debugging and tracking, it is found that the SQL parser engine（SQLParserEngine） logic in 4.1.1 has rewritten? Test SQL : Cannot resolve get condition SELECT * FROM ( SELECT TMP.*, ROWNUM ROW_ID FROM ( SELECT * FROM T_LOG_FWRZ WHERE id = ? AND kssj BETWEEN ? AND ? ORDER BY kssj DESC ) TMP WHERE ROWNUM <=?) WHERE ROW_ID > ?  Test SQL: OK SELECT * FROM T_LOG_FWRZ WHERE id = ? AND kssj BETWEEN ? AND ? ORDER BY kssj DESC  ------ What can I do now? Thank you ### Which version of ShardingSphere did you use? 4.0.0-rc1 to 4.1.1 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC , oracle ### Expected behavior ### Actual behavior ### Reason analyze (If you can) SQLParserEngine Unable to analyze correctly ### 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. For queries about this service, please contact Infrastructure at: [email protected]
