Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 16 Aug 2011 16:09:27 +0000 (UTC)
From: "Kim Haase (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1836455490.41755.1313510967653.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <160079992.41199.1313500888271.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5384) Reference Guide talks about a
 DriverManager method which does not exist.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kim Haase updated DERBY-5384:
-----------------------------

    Issue & fix info: [Patch Available]

> 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