RaigorJiang opened a new issue, #37748: URL: https://github.com/apache/shardingsphere/issues/37748
## Bug Report ### Which version of ShardingSphere did you use? master 1c897e82a4c8c2a24fdcfec772bde63f18b55eb1 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior The openGauss driver can execute transactions normally when accessing the proxy. ### Actual behavior <img width="2852" height="1240" alt="Image" src="https://github.com/user-attachments/assets/5289594f-8879-429c-a2e5-4a69506d7487"; /> ### Reason analyze (If you can) - openGauss driver <img width="2594" height="942" alt="Image" src="https://github.com/user-attachments/assets/bb0254d2-8004-499f-8b7b-16445bb92e50"; /> - PostgreSQL driver <img width="2216" height="1014" alt="Image" src="https://github.com/user-attachments/assets/8fdd424a-ffe6-42b6-8932-73b0d449d9bd"; /> ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1. Start Proxy with openGauss frontend protocol type; 2. Create a JDBC client use openGauss driver; 3. Execute SQL in transaction: ```java private static void queryWithStatementInTransaction(final HikariConfig config) { try (HikariDataSource hikari = new HikariDataSource(config); Connection connection = hikari.getConnection()) { connection.setAutoCommit(false); ResultSet resultSet = connection.createStatement().executeQuery("select * from t_student limit 1;"); while (resultSet.next()) { System.out.printf("%s, %s%n", resultSet.getString(1), resultSet.getString(2)); } connection.commit(); } catch (SQLException e) { throw new RuntimeException(e); } } ``` -- 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]
