Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
10.9.1.0
-
None
-
Normal
Description
The "Accessing databases from the classpath" section of the Derby Developer's Guide says that you can access a database on the classpath by putting a forward slash in front of the database name (and then adding other path legs as needed). I don't find that it works this way. I ran the following experiment:
1) I put a database called nast in the testRun/extin subdirectory of the current directory.
2) Then I put testRun/extin on the classpath.
3) Then I tried connecting to the database with various URLs.
The following URLs could not find the database:
connect 'jdbc:derby:/nast;user=KIWI;password=KIWI_password';
connect 'jdbc:derby:nast;user=KIWI;password=KIWI_password';
connect 'jdbc:derby:classpath:/nast;user=KIWI;password=KIWI_password';
But the following URL found the database:
connect 'jdbc:derby:classpath:nast;user=KIWI;password=KIWI_password';
This is not what I expected from the documentation in the Developer's Guide.
Attachments
Attachments
Issue Links
- relates to
-
DERBY-540 Loading databases from jars in the classpath is broken, databases cannot be found.
- Closed