[ http://issues.apache.org/jira/browse/DERBY-450?page=comments#action_12315498 ]
A B commented on DERBY-450: --------------------------- Thanks for the extra info. After trying unsuccessfully to reproduce this with my local codeline, I then realized that you filed this bug against Derby 10.0, not 10.1 (my local codeline is 10.1). I then tried to use the client URL with Derby 10.0 and saw the same problem that you see. So far as I know, the Derby client isn't officially supported until 10.1. This means that the logic to parse/process a client URL doesn't exist in the 10.0 code for dblook. If you'd like to use the Derby client for your work, I think you'll have to use the Derby 10.1 set of jars. > dblook should be able to use Network Client driver to connect to Network > server > ------------------------------------------------------------------------------- > > Key: DERBY-450 > URL: http://issues.apache.org/jira/browse/DERBY-450 > Project: Derby > Type: New Feature > Components: Tools > Versions: 10.0.2.1 > Reporter: simmi iyer > > Currently dblook can hook to Network server using IBM DB2 driver. > It does not support the database URL for Network Client driver whereas ij > supports this. > Support for drivers by all tools should be consistent. -- 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
