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 2014/09/17 21:11:33 UTC

[jira] [Closed] (DERBY-6647) The ij.driver property is obsolete and need not be documented

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

Kim Haase closed DERBY-6647.
----------------------------

> 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.1.1
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>             Fix For: 10.11.1.1
>
>         Attachments: DERBY-6647-2.diff, DERBY-6647-2.zip, DERBY-6647.diff, DERBY-6647.stat, DERBY-6647.zip
>
>
> 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.3.4#6332)