You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2011/08/16 19:45:27 UTC

[jira] [Resolved] (DERBY-5384) Reference Guide talks about a DriverManager method which does not exist.

     [ https://issues.apache.org/jira/browse/DERBY-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase resolved DERBY-5384.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.9.0.0
                      10.8.1.6
    Issue & fix info:   (was: [Patch Available])

Thanks very much, Rick!

Committed patch DERBY-5384.diff to documentation trunk at revision 1158368.
Merged to 10.8 doc branch at revision 1158391.


> 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
>             Fix For: 10.8.1.6, 10.9.0.0
>
>         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