db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1165772 - in /db/derby/docs/trunk/src/devguide: cdevdvlp40350.dita cdevdvlpinmemdb.dita
Date Tue, 06 Sep 2011 18:12:08 GMT
Author: chaase3
Date: Tue Sep  6 18:12:07 2011
New Revision: 1165772

URL: http://svn.apache.org/viewvc?rev=1165772&view=rev
Log:
DERBY-4637  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

Modified two Developer's Guide topics.

Patch: DERBY-4637.diff

Modified:
    db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita
    db/derby/docs/trunk/src/devguide/cdevdvlpinmemdb.dita

Modified: db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita?rev=1165772&r1=1165771&r2=1165772&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp40350.dita Tue Sep  6 18:12:07 2011
@@ -20,8 +20,8 @@ limitations under the License.
 -->
 <concept id="cdevdvlp40350" xml:lang="en-us">
 <title>Conventions for specifying the database path</title>
-<shortdesc>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
+<shortdesc>When you access databases from the file system (instead of from
+the classpath or a jar file), any path that is not absolute is interpreted as
 relative to the system directory.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm>Databases<indexterm>convention for specifying connection

Modified: db/derby/docs/trunk/src/devguide/cdevdvlpinmemdb.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlpinmemdb.dita?rev=1165772&r1=1165771&r2=1165772&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlpinmemdb.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlpinmemdb.dita Tue Sep  6 18:12:07 2011
@@ -49,6 +49,21 @@ subsubprotocol, you must include it in t
 <p>Be careful to specify a colon (<codeph>:</codeph>) after
 <codeph>memory</codeph>.</p>
 </section>
+<section><title>Referring to in-memory databases</title>
+<p>When you create or refer to an in-memory database, any path that is not
+absolute is interpreted as relative to the system directory, just as with file
+system databases. For example, if the system directory is
+<codeph>C:\myderby</codeph>, the following paths are regarded as
+equivalent:</p>
+<codeblock>jdbc:derby:memory:db
+jdbc:derby:memory:C:\myderby\db</codeblock>
+<p>Similarly, <ph conref="../conrefs.dita#prod/productshortname"></ph>
treats
+the following URLs as names for the same in-memory database:</p>
+<codeblock>jdbc:derby:memory:/home/myname/db
+jdbc:derby:memory:/home/myname/../myname/db</codeblock>
+<p><xref href="cdevdvlp40350.dita#cdevdvlp40350"></xref> has more information
on
+database paths.</p>
+</section>
 <section><title>Using in-memory databases</title>
 <p>When you use an in-memory database, you need to make sure to configure the
 heap and the <ph conref="../conrefs.dita#prod/productshortname"></ph> page



Mime
View raw message