You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2010/04/20 16:58:49 UTC
[jira] Commented: (DERBY-4622) Specify "database:" URL prefix in
documentation
[ https://issues.apache.org/jira/browse/DERBY-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858925#action_12858925 ]
Kristian Waagan commented on DERBY-4622:
----------------------------------------
Hi Chris,
I'm pretty sure Derby expects the protocol to be longer than one char. In that case, this isn't a doc issue, but a bug.
Can you post the exception (and the stack trace if any [1]) you get?
What's the Derby version you are using?
And for good measure, which Windows version?
On Windows XP with Derby 10.5.3 I can connect to the database below in ij:
ij> connect 'jdbc:derby:c:/test/kwdb;create=true'
If I specify s instead of c (non-existing drive), I get:
ERROR XBM0H: Directory S:\test\kwdb cannot be created.
Thanks,
--
[1] With ij, specify -Dij.exceptionTrace=true
> 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.