db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6647) The ij.driver property is obsolete and need not be documented
Date Fri, 11 Jul 2014 19:45:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059253#comment-14059253
] 

Rick Hillegas commented on DERBY-6647:
--------------------------------------

Thanks, Kim. Looks good. A couple comments:

rtoolsdrvrnmeurl

  The jdbc.drivers property still works so I think it should not be
  removed from the documentation: http://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html

ttoolsij97656

  The following statement was made obsolete by the driver autoloading
  improvements introduced by Java 6. Foreign drivers should be
  autoloaded just like Derby's drivers. So this sentence can be removed:

  "Specifying a driver is also required when ij is used with other JDBC drivers to connect
to non-Derby databases."

  And again, the jdbc.drivers property is still a valid way to load a
  driver when the JVM boots.


> 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
>         Attachments: 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.2#6252)

Mime
View raw message