[
https://issues.apache.org/jira/browse/DERBY-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028330#comment-14028330
]
Myrna van Lunteren commented on DERBY-4381:
-------------------------------------------
Adding such a property might be a reasonable request, but I'm not interested at
working towards that at this time.
I agree the lastIndexOf approach is a good improvement. Using a round bracket
in a database name in a jar doesn't work now, and it won't work after the
change; but I think this is an unusual thing to do.
If the round bracket is in the path or jar file name it will work after the
change, and having a round bracket in the path is a common thing - at least on
windows.
I will continue with that fix. I added a test case and am running the full
suite of tests.
> Connection to Derby doesn't work if the path has round braket in it
> --------------------------------------------------------------------
>
> Key: DERBY-4381
> URL: https://issues.apache.org/jira/browse/DERBY-4381
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.5.3.0
> Environment: Windows Vista
> Reporter: Shivaraju Gowda
> Assignee: Myrna van Lunteren
> Labels: derby_triage10_5_2
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> In 64 bit windows vista OS, if an executable is 32 bit than it is generally
> installed under
> "C:\Program Files (x86)" folder. The brackets in the path cause problems
> while connecting
> to any database stored in that folder(in jar format) through derby JDBC.
> The effective connection string is :
> jdbc:derby:jar:(C:/Program Files(86)/ClassicModels.jar)ClassicModels
> This fails because the closing brackets is not escaped.
> I looked into the documentation and didn't find references to escaping the
> brackets in the path.
> I think this problem should be reproducible on all platforms.
> you cannot connect to it,
--
This message was sent by Atlassian JIRA
(v6.2#6252)
