db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4622) Specify "database:" URL prefix in documentation
Date Wed, 21 Apr 2010 13:53:49 GMT

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

Kim Haase commented on DERBY-4622:

I am hesitant to add information about special cases and protocols to the Getting Started
guide, since the instructions there work fine for the elementary tutorial. The more advanced
information is in the Developer's Guide ("Derby JDBC database connection URL") and should
probably stay there. Users who are performing tasks beyond the tutorial level need to refer
to the more advanced Derby documentation in any case. So I would suggest that we refer people
to the topic in the Dev Guide rather than duplicate the information here.

> Specify "database:" URL prefix in documentation
> -----------------------------------------------
>                 Key: DERBY-4622
>                 URL: https://issues.apache.org/jira/browse/DERBY-4622
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Chris Dolan
>            Priority: Trivial
> The tutorial step titled "Activity 3: Run a JDBC program using the embedded driver" at
the following URL (http://db.apache.org/derby/docs/10.4/getstart/getstart-single.html#tgsactivity3_Setup)
recommends this syntax for specifying a directory-based datasource:
>   String connectionURL = "jdbc:derby:" + dbName + ";create=true";
> For Windows users who need to specify an absolute path to the database, this is a problem
because the connection interprets "c:/path/to/db" as non-existent protocol "c" and a database
name of "/path/to/db".  Better documentation would be explicitly specify the protocol:
>   String connectionURL = "jdbc:derby:directory:" + dbName + ";create=true";
> (this would have saved me about a day of troubleshooting...)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message