Repository navigation
jdbc: DriverAction support #174
Description
This interface may be implemented by a driver that wants to be notified by DriverManager when the driver is deregistered.
A DriverAction implementation is not intended to be used directly by applications. A JDBC Driver may choose to create its DriverAction implementation in a private class to avoid it being called directly.
The JDBC driver's static initialization block must call DriverManager.registerDriver(java.sql.Driver, java.sql.DriverAction) in order to inform DriverManager which DriverAction implementation to call when the JDBC driver is de-registered.
Example:
public class SQLDriver implements java.sql.Driver {
static SQLDriverAction driverAction = new SQLDriverAction();
static {
try {
java.sql.DriverManager.registerDriver(new SQLDriver(), driverAction);
} catch (SQLException e) {
throw new RuntimeException("Can't register driver!");
}
}
private class SQLDriverAction implements java.sql.DriverAction {
...
}
}See more here.
Activity
Totktonada commentedon May 12, 2019
What other vendors do for this cases?
nicktorwald commentedon May 13, 2019
It seems others do not implement this interface. They don't restrict any behaviour of already obtained JDBC connections. This affects only Java SPI ability.
DriverActionis a recommendation if we want to be notified after the driver has been deregistered, so I don't see how we can use it now. It's worth closing the issue or moving it to another milestoneTotktonada commentedon Oct 16, 2019
So it does not needed (at least for now) internally and is not a part of public API of a driver. I agree, it worth to close the issue and reopen if we'll need to know about deregistering.