[
https://issues.apache.org/jira/browse/DERBY-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085661#comment-13085661
]
Kristian Waagan commented on DERBY-4637:
----------------------------------------
Would it suffice to rewrite the sentence referred to above, or do we need to
write a new section for in-memory database names?
> The Developer's Guide implies that, for in-memory database names, Derby does
> not resolve relative and absolute paths to the same in-memory database
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4637
> URL: https://issues.apache.org/jira/browse/DERBY-4637
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.6.1.0
> Reporter: Rick Hillegas
>
> The Developer's Guide says in the section titled 'Conventions for specifying
> the database path':
> "When accessing databases from the file system (instead of from memory, the
> classpath, or a jar file), any path that is not absolute is interpreted as
> relative to the system directory."
> A casual reader might interpret this to mean that the system directory is not
> used to resolve paths in the names of in-memory databases. But, in fact,
> Derby does use the system directory to qualify relative paths in the names of
> in-memory databases.
> For instance, if the system directory is /Users/blah/derby/dummy, then Derby
> treats the following urls as identifiers for the same in-memory database:
> jdbc:derby:memory:db
> jdbc:derby:memory:/Users/blah/derby/dummy/db
> Similarly, Derby treats the following urls as names for the same in-memory
> database:
> jdbc:derby:memory:/foo/bar/db
> jdbc:derby:memory:/foo/bar/../bar/db
> The Developer's Guide could use a section on how to resolve in-memory
> database names.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
