fixed QueryExecuter to deal with multiple errors
previously it was throwing a SQLException as soon as the error message was received from the backend. This did not allow the protocol to finish properly now, simply collects error messages from the backend until the query is done and throws exception at the end Also added setLogLevel to Driver.java, and made the log levels public
Showing
Please register or sign in to comment