forked from dork/tarantool-java
-
Notifications
You must be signed in to change notification settings - Fork 19
jdbc: Raise SQLException on Connection methods for a closed connection #72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
nicktorwald
added a commit
that referenced
this issue
Apr 8, 2019
Add missed checks on methods of the closed connection. Add basic implementation Connection.isValid method to check a connection state sending a simple ping request. A support of the timeout param requires implementation of timer task per statement and comes out of the scope this issue. Closes: #72 Affects: #119
nicktorwald
added a commit
that referenced
this issue
Apr 8, 2019
Add missed checks on methods of the closed connection. Add basic implementation Connection.isValid method to check a connection state sending a simple ping request. A support of the timeout param requires implementation of timer task per statement and comes out of the scope this issue. Closes: #72 Affects: #119
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The API states that the exception should be raised when a method is called on a closed connection. It is so for most of the methods. We don't raise it for some 'dumb' methods like getWarnings / clearWarnings, but it seems we must.
The text was updated successfully, but these errors were encountered: