trycache0828 opened a new issue #11536: URL: https://github.com/apache/shardingsphere/issues/11536
## Bug Report When use LIMIT 0, 10, the query result is normal and the number of query result records is 10. When use LIMIT 10, 10, the query result is normal and the number of query result records is 10. But when use LIMIT 20, 10, the query result is incorrect and the number of query result records is 20. https://user-images.githubusercontent.com/14318621/127117069-3ed6036f-a3b6-4d3d-86b0-fada05cbb5ec.png ### Which version of ShardingSphere did you use? <!-- shardingsphere 5.x --> <!-- https://mvnrepository.com/artifact/org.apache.shardingsphere/shardingsphere-jdbc-core --> <dependency> <groupId>org.apache.shardingsphere</groupId> <artifactId>shardingsphere-jdbc-core</artifactId> <version>5.0.0-beta</version> <exclusions> <exclusion> <groupId>org.apache.curator</groupId> <artifactId>curator-client</artifactId> </exclusion> </exclusions> </dependency> ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC ### Expected behavior when use LIMIT 20, 10, the query result is incorrect and the number of query result records is 20. ### Actual behavior use LIMIT 20, 10, the query result is normal and the number of query result records is 10. ### Reason analyze (If you can) SQL parsing query merge result set is not considerate -- 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]
