You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2019/02/27 01:27:04 UTC

[GitHub] baisijian commented on issue #1926: why HOLD_CURSORS_OVER_COMMIT NOT CLOSE_CURSORS_AT_COMMIT

baisijian commented on issue #1926: why HOLD_CURSORS_OVER_COMMIT NOT CLOSE_CURSORS_AT_COMMIT
URL: https://github.com/apache/incubator-shardingsphere/issues/1926#issuecomment-467685508
 
 
   thank you for reply,
   i saw sharding using ResultSet.HOLD_CURSORS_OVER_COMMIT instead of CLOSE_CURSORS_AT_COMMIT , HOLD_CURSORS_OVER_COMMIT is support at jdbc 3.0 ,  If I change  HOLD_CURSORS_OVER_COMMIT  to CLOSE_CURSORS_AT_COMMIT , sharding will still working fine?
   
   code: MasterSlavePreparedStatement.java:50
           this(connection, sql, ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY, ResultSet.HOLD_CURSORS_OVER_COMMIT);
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services