db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-59) dblook currently has driver classes hard coded
Date Sat, 04 Jun 2005 20:52:45 GMT
     [ http://issues.apache.org/jira/browse/DERBY-59?page=all ]
     
Satheesh Bandaram closed DERBY-59:
----------------------------------


Fix has been submitted for sometime.

> dblook currently has driver classes hard coded
> ----------------------------------------------
>
>          Key: DERBY-59
>          URL: http://issues.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://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message