[ http://issues.apache.org/jira/browse/DERBY-618?page=all ]
Deepa Remesh updated DERBY-618:
-------------------------------
Attachment: derby-618-10.1.diff
derby-618-10.1.status
Attaching a patch 'derby-618-10.1.diff' for 10.1 branch. Submiiting a patch
because revision #382917 could not be merged directly using svn merge command.
This patch requires the changes in DERBY-814 to be applied to 10.1 branch
first. This is uploaded as a separate patch at
http://issues.apache.org/jira/browse/DERBY-814. Both these patches need to be
committed together. I would appreciate if someone can look at these patches.
Changes to resove the merge conflicts:
* DERBY-618 - Manual merge was required for the test jdbcapi/checkDriver.java
and masters since 10.1 branch tests hard-code localhost and do not have the
test harness changes to get the host name.
* DERBY-814 - Manual merge was required for DRDAConnThread.java (only conflict
was in javadoc comments) and Database.java (had to change two methods to use
the new class Pkgnamcsn)
With both the patches applied, I ran the following tests:
* derbyall with sane jars using Sun JDK 1.4.2. One failure in
unit/T_Diagnosticable.unit. This test is failing with sane jars. It does not
fail with sane classes. The test fails with sane jars even without the patches.
The failure is same as what is reported in DERBY-496.
* jdbcapi/checkDriver.java with j9 vms.
NOTE: This patch has to be committed together with the 10.1 branch patch for
DERBY-814 (derby-814-10.1.diff).
> Make the client driver connection URL work when spaces are in the URL.
> ----------------------------------------------------------------------
>
> Key: DERBY-618
> URL: http://issues.apache.org/jira/browse/DERBY-618
> Project: Derby
> Type: Improvement
> Components: Network Client
> Versions: 10.1.1.0
> Reporter: Trejkaz
> Assignee: Deepa Remesh
> Fix For: 10.1.2.4, 10.2.0.0, 10.1.3.0
> Attachments: derby-618-10.1.diff, derby-618-10.1.status,
> derby-618-script.sql, derby-618-v1.diff, derby-618-v1.status,
> derby-618-v2.diff, derby-618-v2.status, derby-618.java
>
> At present, if I want to connect to a database on a Derby server which has a
> space in the path, there is no way to do it.
> This can be done with the embedded driver, and for consistency it would be
> good if it worked for the client driver in the same fashion.
--
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
