Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 2 Jul 2014 21:10:26 +0000 (UTC)
From: "Kim Haase (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12725099.1404335407819.91305.1404335426589@arcas>
In-Reply-To: <JIRA.12725099.1404335407819@arcas>
References: <JIRA.12725099.1404335407819@arcas>
Subject: [jira] [Created] (DERBY-6647) The ij.driver property is obsolete
 and need not be documented
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kim Haase created DERBY-6647:
--------------------------------

             Summary: The ij.driver property is obsolete and need not be documented
                 Key: DERBY-6647
                 URL: https://issues.apache.org/jira/browse/DERBY-6647
             Project: Derby
          Issue Type: Improvement
          Components: Documentation
    Affects Versions: 10.11.0.0
            Reporter: Kim Haase
            Assignee: Kim Haase
            Priority: Minor


The ij.driver property is not useful any more and can be removed from the documentation. According to Rick Hillegas, "The purpose of the ij.driver property is to tell ij to manually load a driver class via Class.forName().newInstance(). That's the ancient way of loading drivers. The modern way is to rely on driver autoloading."

The Driver command may still be useful for reloading the driver after the Derby engine has been shut down and the driver deregistered, so that can be kept.


--
This message was sent by Atlassian JIRA
(v6.2#6252)