Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

• Searched open and closed GitHub issues.
• Read documentation: ShardingSphere Doc.

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?

5.5.1

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-Proxy

Expected behavior

Actual behavior

Reason analyze (If you can)

Printing in the log, it is found that the parameters after limit are caused by the order problem

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

1、 CREATE TABLE employees ( id SERIAL PRIMARY KEY, name VARCHAR(50) NOT NULL, age INT CHECK (age > 18), department VARCHAR(50), salary DECIMAL(10,2) );

2、 INSERT INTO opengauss.employees (id, "name", age, department, salary) VALUES(1, '张三', 28, '研发', 12000.50); INSERT INTO opengauss.employees (id, "name", age, department, salary) VALUES(2, '李四', 29, '市场', 10800.00); INSERT INTO opengauss.employees (id, "name", age, department, salary) VALUES(3, '王五', 30, '销售', 12000.50); INSERT INTO opengauss.employees (id, "name", age, department, salary) VALUES(4, '赵六', 31, '经理', 20215.25);

3、 String sql = "SELECT * FROM employees order by id limit ? , ?;"; PreparedStatement psmt = conn.prepareStatement(sql); psmt.setInt(1,2); psmt.setInt(2,1);

Example codes for reproduce this issue (such as a github link).