Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
1.1.5
-
None
-
None
-
JDK 1.7
Description
Hi,
jdbc4 got the new "abort" method on a connection (the mysql jdbc driver from oracle does implement this) and i am using this in case i need to forcefully close the connection.
Tried this with MariaDB driver and all seems fine - no exception, but the connection did leak - so i wonder.
Looking at the source is see this:
public void abort(Executor arg0) throws SQLException {
|
// TODO Auto-generated method stub
|
|
}
|
|
public int getNetworkTimeout() throws SQLException {
|
// TODO Auto-generated method stub
|
return 0;
|
}
|
|
public String getSchema() throws SQLException {
|
// TODO Auto-generated method stub
|
return null;
|
}
|
|
public void setNetworkTimeout(Executor arg0, int arg1) throws SQLException {
|
// TODO Auto-generated method stub
|
|
}
|
|
public void setSchema(String arg0) throws SQLException {
|
// TODO Auto-generated method stub
|
|
}
|
Please - just throw an UnsupportedOperationException or a SQLException telling the user that you did not implemented this yet, but silently discard this call, leaving the caller with the wrong assumption that the operation did succeed, is imho not the way it should be.
Attachments
Issue Links
- relates to
-
CONJ-75 Implement useful jdbc4 abort(Executor arg) method on MySQLConnection
- Closed