Derby
  1. Derby
  2. DERBY-59

dblook currently has driver classes hard coded

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.0.2.0
    • Component/s: Tools
    • Labels:
      None

      Description

      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).

        Activity

        Hide
        Satheesh Bandaram added a comment -

        Fix has been submitted for sometime.

        Show
        Satheesh Bandaram added a comment - Fix has been submitted for sometime.
        Hide
        Satheesh Bandaram added a comment -

        I have submitted this patch. Thanks Jon.

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

        Show
        Satheesh Bandaram added a comment - I have submitted this patch. Thanks Jon. Sending java\tools\org\apache\derby\tools\dblook.java Transmitting file data . Committed revision 105887.
        Hide
        Jon Craven added a comment -

        Trivial patch to load the driver the same way as in ij.

        Show
        Jon Craven added a comment - Trivial patch to load the driver the same way as in ij.

          People

          • Assignee:
            Unassigned
            Reporter:
            John Sisson
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development