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 Wed, 01 Mar 2006 01:33:42 GMT
     [ http://issues.apache.org/jira/browse/DERBY-618?page=all ]

Deepa Remesh updated DERBY-618:

    Attachment: derby-618.java

Ataching repros to test the patch:

1. repro1: derby-618.java - This is a simple java program which creates and connects to a
database with spaces in path. And then does some operations on the database. 

2. repro2: derby-618-script.sql - This is an ij script.

To run the repros:
1. Start network server on port 2222.
2. For repro1, run the command 'java derby-618'.
3. For repro 2, start ij and run the script 'derby-618-script.sql'.

Without the patch:
The repros will not give any exception when run without the patch. They will just create the
wrong databases:
* repro1 will create a database 'C:\directory'
* repro2 will create a database 'test'

With the patch:
Repros should create the correct databases with spaces:
* repro1 will create 'C:\directory with spaces\db name with spaces'
* repro2 will create 'test db with spaces'

> 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.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