JiekerTime opened a new issue #11365: URL: https://github.com/apache/shardingsphere/issues/11365
### 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  ### Actual behavior   ### Reason analyze (If you can) Metadata order error in proxy scenario. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. #### The first way Modify the integration test configuration file as follows:  Execute case as follow:  #### The Second way Start a proxy service with the configuration file in [SS](https://github.com/apache/shardingsphere/blob/master/shardingsphere-test/shardingsphere-integration-test/shardingsphere-integration-test-suite/src/test/resources/docker/db/postgresql/proxy/conf/config-db.yaml). Initialize the database using the [init.sql](https://github.com/apache/shardingsphere/blob/master/shardingsphere-test/shardingsphere-integration-test/shardingsphere-integration-test-suite/src/test/resources/env/db/init-sql/postgresql/init.sql); Execute statement “SELECT * FROM t_broadcast_table” Observation metadata:  -- 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]
