Y-sir opened a new issue, #34267: URL: https://github.com/apache/shardingsphere/issues/34267
## 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? 5.5.1 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior In the original MySQL database, the execution result is successful  ### Actual behavior 1064 - You have an error in your SQL syntax: no viable alternative at input 't.order' near '[@32,139:143='order',<508>,11:4]' at line 11 ### Reason analyze (If you can) ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1、Create a table `CREATE TABLE `xxl_job_user` ( `id` int NOT NULL AUTO_INCREMENT, `username` varchar(50) NOT NULL COMMENT '账号', `password` text CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT '密码', `role` tinyint NOT NULL COMMENT '角色：0-普通用户、1-管理员', `permission` varchar(255) DEFAULT NULL COMMENT '权限：执行器ID列表，多个逗号分割', PRIMARY KEY (`id`), UNIQUE KEY `i_username` (`username`) USING BTREE ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb3;` 2、Execute a query statement `SELECT t.id, t.app_name, t.title, t.`order`, t.address_type, t.address_list FROM xxl_job_group AS t ORDER BY t.order ASC;` 3、In the original MySQL database, execute  4、In the proxy database, the execution result is as follows  ### 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]
