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 "Satheesh Bandaram (JIRA)" <de...@db.apache.org> on 2004/11/24 01:31:22 UTC

[jira] Resolved: (DERBY-59) dblook currently has driver classes hard coded

     [ http://nagoya.apache.org/jira/browse/DERBY-59?page=history ]
     
Satheesh Bandaram resolved DERBY-59:
------------------------------------

     Resolution: Fixed
    Fix Version: 10.0.2.0

I have submitted this patch. Thanks Jon.

Sending        java\tools\org\apache\derby\tools\dblook.java
Transmitting file data .
Committed revision 105887.

> dblook currently has driver classes hard coded
> ----------------------------------------------
>
>          Key: DERBY-59
>          URL: http://nagoya.apache.org/jira/browse/DERBY-59
>      Project: Derby
>         Type: Task
>   Components: Tools
>     Reporter: John Sisson
>     Priority: Trivial
>      Fix For: 10.0.2.0
>  Attachments: DERBY-59.diff
>
> Just noting this whilst looking at the dblook code..  I have no current need for it at the moment..
> Currently the loadDriver() function in dblook.java uses one of two hard coded drivers (com.ibm.db2.jcc.DB2Driver or org.apache.derby.jdbc.EmbeddedDriver) based upon the URL supplied on the command.
> In the future, an alternative driver may be used, so dblook should allow the driver to be specified (e.g. the ij tool allows this to be specified via properties).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira