Currently there is no easy way to get the JDBCDriver instance that a
DatabaseConnection will use / used to connect to a database. A
DatabaseConnection.getJDBCDriver() method should be added.
Will be used by the deployment of JDBC drivers to the application server.
I heard a workaround was determined and so adding getJDBCDriver() is no longer
needed. This issue will be closed. If the method is still needed then this
issue can be reopened
Reopening - I am not sure what workaround has jbaker in mind. If it was
then this workaround existed at the time this issue was filled and therefore
changes nothing on its status. It still would be nice to have a clean way to
obtain the driver from the connection.
I am changing this to a P3 defect, as it blocks another P3 defect (issue 119644). It would be great to have this
implemented for 6.7. Thanks.
Created attachment 81660 [details]
a proposed patch
Please review my changes.
I'm going to integrate it tomorrow.
integrated in core-main/rev/c15a86ef59d3