Github user mattyb149 commented on the issue:
    I think for the setQueryTimeout() we should use the approach 
 It was decided a while back that we should enforce setQueryTimeout() instead 
of just proceeding on if the driver doesn't support it. What the code in the 
other PR (#2138) does is to try to call setQueryTimeout on a Statement during 
customValidate, and will render the processor invalid if the user tries to set 
a Query Timeout to something other than zero when the driver doesn't support it.


Reply via email to