Deepa, Is there an extra "not" in your comments? I don't understand how a fix could involve removing the ability to parse standard URL escape sequences. Spaces are not valid[1] in URIs and therefore are disallowed in URLs.
thanx, doug [1] <http://www.ietf.org/rfc/rfc3986.txt> On 8/23/06, Deepa Remesh <[EMAIL PROTECTED]> wrote:
On 8/22/06, Ray Kiddy <[EMAIL PROTECTED]> wrote: > > On Aug 4, 2006, at 7:11 AM, Bryan Pendleton wrote: > > >> Trying to create a dataset using BIRT report's designer i have > >> faced a > >> problem related with white spaces in connection urls. > > > > I believe this is DERBY-618: > > http://issues.apache.org/jira/browse/DERBY-618 > > which has been fixed, and the fix is in Derby version 10.1.2.4. > > > > Can you upgrade to that version and tell us if the fix works for you? > > > > thanks, > > > > bryan > > How has this been fixed? This has been fixed by changing the the client driver code. Derby drivers parse the connection URL (not using Java URL class) to check for the expected format. So Derby does not recognize the URL escape sequence for space "%20". Thanks, Deepa
