db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-618) Make the client driver connection URL work when spaces are in the URL.
Date Fri, 03 Mar 2006 03:56:50 GMT
     [ http://issues.apache.org/jira/browse/DERBY-618?page=all ]

Deepa Remesh updated DERBY-618:

    Attachment: derby-618-v2.diff

Attaching a patch 'derby-618-v2.diff' which includes code change and a test for this issue.
Patch does the following:

* Modifies ClientDriver.java - removes the space separator in the call to nextToken in tokenizeDatabase
method. This allows use of URL containing database name with spaces. 

* Adds tests to jdbcapi/checkDriver.java for an url with spaces in database name. Since embedded
and jcc driver work with spaces, I added this test for all three frameworks. Test verfies
that the specified database gets created.

* Modifies master files for the test

Ran derbyall with Sun JDK 1.4.2 on Windows XP. I also ran jdbcapi/checkDriver.java with j9
vms. Please take a look at this patch. Thanks.

> 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:
>     Reporter: Trejkaz
>     Assignee: Deepa Remesh
>  Attachments: 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:
For more information on JIRA, see:

View raw message