[ http://issues.apache.org/jira/browse/DERBY-1217?page=comments#action_12421529 ] Andrew McIntyre commented on DERBY-1217: ----------------------------------------
One note: with the patch, connections to the network server or JCC don't work unless the full protocol string is specified. This is similar to the current situation where ij.protocol="jdbc:derby:" and you attempt to connect with "connect '//localhost/mydb';". While this is expected, we may want to address the problem of subprotocol specifications with this issue as well. > ij should default to protocol 'jdbc:derby:' if no protocol is passed in > through ij.protocol > ------------------------------------------------------------------------------------------- > > Key: DERBY-1217 > URL: http://issues.apache.org/jira/browse/DERBY-1217 > Project: Derby > Issue Type: Improvement > Components: Tools > Affects Versions: 10.2.0.0, 10.1.3.0 > Reporter: Andrew McIntyre > Priority: Minor > Attachments: derby-1217-pre.diff > > > If no default protocol is set by passing in one with ij.protocol, ij should > default to 'jdbc:derby:' . > See the thread 'default ij protocol' for details: > http://mail-archives.apache.org/mod_mbox/db-derby-dev/200602.mbox/[EMAIL > PROTECTED] -- 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
