[ 
https://issues.apache.org/jira/browse/DERBY-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254763#comment-13254763
 ] 

Knut Anders Hatlen commented on DERBY-5612:
-------------------------------------------

> I don't understand why the "standard syntax" in tdevdeploy39856 is wrong, 
> though.

It lacks the classpath subsubprotocol that's required to access a database in a 
jar on the classpath, and it has a leading slash. If those two problems are 
fixed, it becomes identical to the other URL mentioned there, so it can be 
removed.

> It seems to be the same as what is shown in 
> http://db.apache.org/derby/docs/dev/devguide/cdevdvlp24155.html for accessing 
> jar files.

Yes, that one looks wrong too. :)

> Another possible discovery in the revised "Database connection examples" 
> (rdevdvlp22102): Under the third bullet, on the example 
> jdbc:derby:/reference/phrases/french, should the last sentence be removed?

Yes, I believe so. In the same topic, the eighth bullet (jdbc:derby:/myDB) 
should be removed, the tenth bullet (jdbc:derby:classpath:myDB) should have its 
last sentence removed, and the twelfth bullet (jdbc:derby:directory:myDB) 
should have its last sentence removed too.

Do you think we've found them all now? :)
                
> Puzzling documentation about the URL to a database on the classpath
> -------------------------------------------------------------------
>
>                 Key: DERBY-5612
>                 URL: https://issues.apache.org/jira/browse/DERBY-5612
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.9.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-5612.diff, DERBY-5612.stat, DERBY-5612.zip
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to