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 "John Sisson (JIRA)" <de...@db.apache.org> on 2004/11/08 05:06:32 UTC
[jira] Created: (DERBY-59) dblook currently has driver classes hard coded
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
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
[jira] Updated: (DERBY-59) dblook currently has driver classes hard coded
Posted by "Jon Craven (JIRA)" <de...@db.apache.org>.
[ http://nagoya.apache.org/jira/browse/DERBY-59?page=history ]
Jon Craven updated DERBY-59:
----------------------------
Attachment: DERBY-59.diff
Trivial patch to load the driver the same way as in ij.
> 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
> 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
[jira] Closed: (DERBY-59) dblook currently has driver classes hard coded
Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Resolved: (DERBY-59) dblook currently has driver classes hard coded
Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
[ 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