JiekerTime opened a new issue #11382:
URL: https://github.com/apache/shardingsphere/issues/11382


   ### Which version of ShardingSphere did you use?
   5.0.0-RC1-SNAPSHOT
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy
   
   ### Expected behavior
   
![image](https://user-images.githubusercontent.com/76552510/126105320-d3a6897e-2264-4d54-b325-2b0827dfd2e8.png)
   
   ### Actual behavior
   
![image](https://user-images.githubusercontent.com/76552510/126105376-dca6865f-cc34-4f8b-9919-8b4b387e343d.png)
   
![image](https://user-images.githubusercontent.com/76552510/126105420-e3d98eb7-2f10-4c1d-8bdb-a0a03ac5f164.png)
   
   ### Reason analyze (If you can)
   There is a problem with the metadata in the Proxy scenario.
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   Please refer to the integration test for the [configuration 
file](https://github.com/apache/shardingsphere/blob/master/shardingsphere-test/shardingsphere-integration-test/shardingsphere-integration-test-suite/src/test/resources/docker/tbl/postgresql/proxy/conf/config-tbl.yaml)
 and 
[init.sql](https://github.com/apache/shardingsphere/blob/master/shardingsphere-test/shardingsphere-integration-test/shardingsphere-integration-test-suite/src/test/resources/env/tbl/init-sql/postgresql/init.sql)
   
   Execute "SELECT o.order_id as gen_order_id_ FROM t_order o ORDER BY 
o.order_id"
   


-- 
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]


Reply via email to