[GitHub] [shardingsphere] always-busy opened a new issue, #25154: logSlowQuery should print sql instead of statement.toString()

["always-busy (via GitHub)" <gi...@apache.org>]

always-busy opened a new issue, #25154:
URL: https://github.com/apache/shardingsphere/issues/25154

   
   
   ### Which version of ShardingSphere did you use?
   shardingsphere5.3.1
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-JDBC
   
   ### Expected behavior
   Actually，logSlowQuery method should print sql 
   
   ### Actual behavior
   SlowQuery: 19621 milliseconds. SQL: 'org.apache.shardingsphere.driver.jdbc.core.statement.ShardingSpherePreparedStatement@714ccc92'
   
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   
   ### 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: notifications-unsubscribe@shardingsphere.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [shardingsphere] Pace2Car commented on issue #25154: logSlowQuery should print sql instead of statement.toString()

["Pace2Car (via GitHub)" <gi...@apache.org>]

Pace2Car commented on issue #25154:
URL: https://github.com/apache/shardingsphere/issues/25154#issuecomment-1506672548

   Please provide more information to troubleshoot.


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org