[ https://issues.apache.org/jira/browse/DERBY-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-5384: ----------------------------- Attachment: DERBY-5384.zip DERBY-5384.stat DERBY-5384.diff Actually, two topics mention the unload method; the other is "Derby JDBC driver" in the Developer's Guide. Attaching DERBY-5384.diff, DERBY-5384.stat, and DERBY-5384.zip, with these changes: M src/devguide/cdevdvlp40653.dita M src/ref/rrefjdbc32052.dita > Reference Guide talks about a DriverManager method which does not exist. > ------------------------------------------------------------------------ > > Key: DERBY-5384 > URL: https://issues.apache.org/jira/browse/DERBY-5384 > Project: Derby > Issue Type: Bug > Components: Documentation > Affects Versions: 10.9.0.0 > Reporter: Rick Hillegas > Assignee: Kim Haase > Attachments: DERBY-5384.diff, DERBY-5384.stat, DERBY-5384.zip > > > The section titled "java.sql.Driver interface" in the Reference Guide > mentions the DriverManager.unload() method. There is no such method. I > believe that DriverManager.deregisterDriver() is intended. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira