| Key: |
DERBY-59
|
| Type: |
Task
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Trivial
|
| Assignee: |
Unassigned
|
| Reporter: |
John Sisson
|
| Votes: |
1
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
24/Nov/04 12:28 AM
|
|
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).
|
|
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). |
Show » |
made changes - 09/Nov/04 10:45 PM
| Field |
Original Value |
New Value |
|
Attachment
|
|
DERBY-59.diff
[ 18100
]
|
Satheesh Bandaram made changes - 24/Nov/04 12:28 AM
|
Fix Version/s
|
|
10.0.2.0
[ 10920
]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
Satheesh Bandaram made changes - 05/Jun/05 05:45 AM
|
Status
|
Resolved
[ 5
]
|
Closed
[ 6
]
|
|
dblook currently has driver classes hard coded
