TedCraft opened a new issue, #39926: URL: https://github.com/apache/shardingsphere/issues/39926
## 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? latest (tested on commit [0496849](https://github.com/apache/shardingsphere/commit/04968495bb7bde791f98a58a9bd416f198a76380)) ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? Both ShardingSphere-JDBC and ShardingSphere-Proxy ### Expected behavior When executing SQL query `SELECT * FROM T_ORDER ORDER BY ID OFFSET 100000 ROWS FETCH FIRST 10 ROWS ONLY` it should be rewritten as `SELECT * FROM T_ORDER ORDER BY ID OFFSET 0 ROWS FETCH FIRST 100010 ROWS ONLY` according to documentation ### Actual behavior The SQL query was not rewritten as expected and is executed as `SELECT * FROM T_ORDER ORDER BY ID OFFSET 100000 ROWS FETCH FIRST 10 ROWS ONLY` ### Reason analyze (If you can) The `limitClause` rule in Firebird BaseRule.g4 lacks a `visit` function in FirebirdStatementVisitor that creates a `LimitSegment` (similar to `visitFirstSkipClause` in FirebirdDMLStatementVisitor). ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. SQL: `SELECT * FROM T_ORDER ORDER BY ID OFFSET 100000 ROWS FETCH FIRST 10 ROWS ONLY` ### 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]
