You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by sc...@apache.org on 2007/03/30 17:19:21 UTC
svn commit: r524120 [2/3] - /db/derby/docs/trunk/src/ref/
Modified: db/derby/docs/trunk/src/ref/rreffuncxmlparse.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreffuncxmlparse.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rreffuncxmlparse.dita (original)
+++ db/derby/docs/trunk/src/ref/rreffuncxmlparse.dita Fri Mar 30 08:19:13 2007
@@ -21,7 +21,7 @@
<reference id="rreffuncxmlparse" xml:lang="en-us">
<title>XMLPARSE operator</title>
<shortdesc>XMLPARSE is a SQL/XML operator that you use to parse a character
-string expression into a <ph conref="refconrefs.dita#prod/productshortname"></ph> XML
+string expression into a <ph conref="../conrefs.dita#prod/productshortname"></ph> XML
value.</shortdesc>
<prolog><metadata>
<keywords><indexterm>XMLPARSE operator</indexterm><indexterm>operators<indexterm>XMLPARSE</indexterm></indexterm>
@@ -29,21 +29,21 @@
</metadata></prolog>
<refbody>
<section> <p>You can use the result of this operator temporarily or you can
-store the result permanently in <ph conref="refconrefs.dita#prod/productshortname"></ph> XML
+store the result permanently in <ph conref="../conrefs.dita#prod/productshortname"></ph> XML
columns. Whether temporary or permanent, you can use the XML value as an
-input to the other <ph conref="refconrefs.dita#prod/productshortname"></ph> XML
+input to the other <ph conref="../conrefs.dita#prod/productshortname"></ph> XML
operators, such as <xref href="rreffuncxmlexists.dita#rreffuncxmlexists">XMLEXISTS</xref> and <xref
href="rreffuncxmlquery.dita#rreffuncxmlquery">XMLQUERY</xref>.</p> </section>
<refsyn><title>Syntax</title><codeblock><b>XMLPARSE (DOCUMENT <varname>string-value-expression</varname> PRESERVE WHITESPACE)</b></codeblock><dl>
<dlentry>
<dt>DOCUMENT </dt>
-<dd> <p>Required keyword that describes the type of XML input that <ph conref="refconrefs.dita#prod/productshortname"></ph> can
-parse. <ph conref="refconrefs.dita#prod/productshortname"></ph> can only
+<dd> <p>Required keyword that describes the type of XML input that <ph conref="../conrefs.dita#prod/productshortname"></ph> can
+parse. <ph conref="../conrefs.dita#prod/productshortname"></ph> can only
parse string expressions that constitute well-formed XML documents. This
-is because <ph conref="refconrefs.dita#prod/productshortname"></ph> uses a
+is because <ph conref="../conrefs.dita#prod/productshortname"></ph> uses a
JAXP parser to parse all string values. The JAXP parser expects the string-value-expression
to constitute a well-formed XML document. If the string does not constitute
-a well-formed document, JAXP throws an error. <ph conref="refconrefs.dita#prod/productshortname"></ph> catches
+a well-formed document, JAXP throws an error. <ph conref="../conrefs.dita#prod/productshortname"></ph> catches
the error and throws the error as a SQLException.</p></dd>
</dlentry><dlentry>
<dt><codeph>string-value-expression</codeph></dt>
@@ -51,21 +51,21 @@
LONG VARCHAR, or CLOB. The <codeph>string-value-expression</codeph> argument
can also be a parameter. You must use the CAST function when you specify the
parameter to indicate the type of value that is bound into the parameter. <ph
-conref="refconrefs.dita#prod/productshortname"></ph> must verify that the
+conref="../conrefs.dita#prod/productshortname"></ph> must verify that the
parameter is the correct data type before the value is parsed as an XML document.
If a parameter is specified without the CAST function, or if the CAST is
-to a non-character datatype, <ph conref="refconrefs.dita#prod/productshortname"></ph> throws
+to a non-character datatype, <ph conref="../conrefs.dita#prod/productshortname"></ph> throws
an error.</dd>
</dlentry><dlentry>
<dt>PRESERVE WHITESPACE</dt>
-<dd>Required keywords that describe how <ph conref="refconrefs.dita#prod/productshortname"></ph> handles
+<dd>Required keywords that describe how <ph conref="../conrefs.dita#prod/productshortname"></ph> handles
whitespace between consecutive XML nodes. When the PRESERVE WHITESPACE keywords
-are used, <ph conref="refconrefs.dita#prod/productshortname"></ph> preserves
+are used, <ph conref="../conrefs.dita#prod/productshortname"></ph> preserves
whitespace as dictated by the SQL/XML rules for preserving whitespace.</dd>
</dlentry></dl><p>For more information on what constitutes a well-formed XML
document, see the following specification: <xref format="html" href="http://www.w3.org/TR/REC-xml/#sec-well-formed">http://www.w3.org/TR/REC-xml/#sec-well-formed </xref
>.</p><p><note type="restriction">The SQL/XML standard dictates that the argument
-to the XMLPARSE operator can also be a binary string. However, <ph conref="refconrefs.dita#prod/productshortname"></ph> only
+to the XMLPARSE operator can also be a binary string. However, <ph conref="../conrefs.dita#prod/productshortname"></ph> only
supports character string input for the XMLPARSE operator.</note></p></refsyn>
<section><title>Examples</title><p>To insert a simple XML document into the <codeph>xcol</codeph> XML
column in the <codeph>x_table</codeph> table, use the following statement: <codeblock>INSERT INTO <varname>x_table</varname> VALUES
@@ -86,7 +86,7 @@
)
</codeblock>You should bind into the statement using the setCharacterStream()
method, or any other JDBC setXXX method that works for the CAST target type.</p></section>
-<section><title>Usage note</title><p><ph conref="refconrefs.dita#prod/productshortname"></ph> requires
+<section><title>Usage note</title><p><ph conref="../conrefs.dita#prod/productshortname"></ph> requires
that a JAXP parser, such as Apache Xerces, and that Apache Xalan are listed
in the Java classpath for the XML functions to work. If either the JAXP parser
or Xalan is missing from the classpath, attempts to use the XMLPARSE operator
Modified: db/derby/docs/trunk/src/ref/rreffuncxmlquery.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreffuncxmlquery.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rreffuncxmlquery.dita (original)
+++ db/derby/docs/trunk/src/ref/rreffuncxmlquery.dita Fri Mar 30 08:19:13 2007
@@ -28,7 +28,7 @@
</metadata></prolog>
<refbody>
<section> <p>The XMLQUERY operator has two arguments, an XML query expression
-and a <ph conref="refconrefs.dita#prod/productshortname"></ph> XML value.</p></section>
+and a <ph conref="../conrefs.dita#prod/productshortname"></ph> XML value.</p></section>
<refsyn><title>Syntax</title><codeblock><b>XMLQUERY ( <varname>xquery-string-literal</varname>
PASSING BY REF <varname>xml-value-expression</varname>
[ RETURNING SEQUENCE [ BY REF ] ]
@@ -37,12 +37,12 @@
<dt><codeph>xquery-string-literal</codeph></dt>
<dd>Must be specified as a string literal. If this argument is specified as
a parameter, an expression that is not a literal, or a literal that is not
-a string (for example an integer),<ph conref="refconrefs.dita#prod/productshortname"></ph> throws
+a string (for example an integer),<ph conref="../conrefs.dita#prod/productshortname"></ph> throws
an error. The <codeph>xquery-string-literal</codeph> argument must also be
-an XPath expression that is supported by Apache Xalan. <ph conref="refconrefs.dita#prod/productshortname"></ph> uses
+an XPath expression that is supported by Apache Xalan. <ph conref="../conrefs.dita#prod/productshortname"></ph> uses
Apache Xalan to evaluate all XML query expressions. Because Xalan does not
-support full XQuery, neither does <ph conref="refconrefs.dita#prod/productshortname"></ph>.
-If Xalan is unable to compile or execute the query argument, <ph conref="refconrefs.dita#prod/productshortname"></ph> catches
+support full XQuery, neither does <ph conref="../conrefs.dita#prod/productshortname"></ph>.
+If Xalan is unable to compile or execute the query argument, <ph conref="../conrefs.dita#prod/productshortname"></ph> catches
the error that is thrown by Xalan and throws the error as a SQLException.
For more on XPath and XQuery expressions, see these Web sites: <xref format="html"
href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</xref> and <xref
@@ -51,24 +51,24 @@
<dt><codeph>xml-value-expression</codeph></dt>
<dd>Must be an XML data value and must constitute a well-formed SQL/XML document.
The <codeph>xml-value-expression</codeph> argument cannot be a parameter.
- <ph conref="refconrefs.dita#prod/productshortname"></ph> does not perform
+ <ph conref="../conrefs.dita#prod/productshortname"></ph> does not perform
implicit parsing nor casting of XML values, so use of strings or any other
data type results in an error. If the argument is a sequence that is returned
-by a <ph conref="refconrefs.dita#prod/productshortname"></ph> XMLQUERY operation,
+by a <ph conref="../conrefs.dita#prod/productshortname"></ph> XMLQUERY operation,
the argument is accepted if it is a sequence of exactly one node that is a
-document node. Otherwise <ph conref="refconrefs.dita#prod/productshortname"></ph> throws
+document node. Otherwise <ph conref="../conrefs.dita#prod/productshortname"></ph> throws
an error. </dd>
</dlentry><dlentry>
<dt>BY REF</dt>
<dd>Optional keywords that describe the only value passing mechanism supported
-by <ph conref="refconrefs.dita#prod/productshortname"></ph>. Since BY REF
+by <ph conref="../conrefs.dita#prod/productshortname"></ph>. Since BY REF
is also the default passing mechanism, the XMLQUERY operator behaves the same
whether the keywords are present or not. For more information on passing mechanisms,
see the SQL/XML specification.</dd>
</dlentry><dlentry>
<dt>RETURNING SEQUENCE</dt>
<dd>Optional keywords that describe the only XML type returned by the <ph
-conref="refconrefs.dita#prod/productshortname"></ph> XMLQUERY operator. Since
+conref="../conrefs.dita#prod/productshortname"></ph> XMLQUERY operator. Since
SEQUENCE is also the default return type, the XMLQUERY operator behaves the
same whether the keywords are present or not. For more information on the
different XML return types, see the SQL/XML specification.</dd>
@@ -78,7 +78,7 @@
result sequence. The XMLQUERY operator returns an empty sequence exactly as
the sequence is. The XMLQUERY operator does not convert the empty sequence
to a null value. When an empty result sequence is serialized, the result
-is an empty string. <ph conref="refconrefs.dita#prod/productshortname"></ph> does
+is an empty string. <ph conref="../conrefs.dita#prod/productshortname"></ph> does
not consider an empty result sequence to be a well-formed XML document.</dd>
</dlentry></dl><p>The result of the XMLQUERY operator is a value of type XML.
The result represents a sequence of XML nodes or values. Atomic values, such
@@ -109,7 +109,7 @@
XMLEXISTS('<varname>//student[text() = "BC"]</varname>' PASSING BY REF <varname>xcol</varname>)
</codeblock> The result set for this query contains a row for only the rows
in <codeph>x_table</codeph> that have a student whose name is BC.</p></section>
-<section><title>Usage note</title><p><ph conref="refconrefs.dita#prod/productshortname"></ph> requires
+<section><title>Usage note</title><p><ph conref="../conrefs.dita#prod/productshortname"></ph> requires
that a JAXP parser, such as Apache Xerces, and that Apache Xalan are listed
in the Java classpath for the XML functions to work. If either the JAXP parser
or Xalan is missing from the classpath, attempts to use the XMLQUERY operator
Modified: db/derby/docs/trunk/src/ref/rreffuncxmlserialize.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreffuncxmlserialize.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rreffuncxmlserialize.dita (original)
+++ db/derby/docs/trunk/src/ref/rreffuncxmlserialize.dita Fri Mar 30 08:19:13 2007
@@ -22,14 +22,14 @@
<title>XMLSERIALIZE operator</title>
<shortdesc>XMLSERIALIZE is a SQL/XML operator that you can use to convert
an XML type to a character type. There is no other way to convert the type
-of a <ph conref="refconrefs.dita#prod/productshortname"></ph> XML value.</shortdesc>
+of a <ph conref="../conrefs.dita#prod/productshortname"></ph> XML value.</shortdesc>
<prolog><metadata>
<keywords><indexterm>XMLSERIALIZE operator</indexterm><indexterm>operators<indexterm>XMLSERIALIZE</indexterm></indexterm>
<indexterm>XML<indexterm>operators, XMLSERIALIZE</indexterm></indexterm></keywords>
</metadata></prolog>
<refbody>
<section> <note type="attention">Serialization is performed based on the SQL/XML
-serialization rules. These rules, combined with the fact that <ph conref="refconrefs.dita#prod/productshortname"></ph> supports
+serialization rules. These rules, combined with the fact that <ph conref="../conrefs.dita#prod/productshortname"></ph> supports
only a subset of the XMLSERIALIZE syntax, dictate that the results of an XMLSERIALIZE
operation are not guaranteed to be in-tact copies of the original XML text.
For example, assume that <codeph>[xString]</codeph> is a textual representation
@@ -49,8 +49,8 @@
be accessed from JDBC by using whatever JDBC getXXX methods are allowed on
the <codeph>string-data-type</codeph> argument that is included in the XMLSERIALIZE
syntax. If you attempt to select the contents of an XML value from a top-level
-result set without using the XMLSERIALIZE operator, <ph conref="refconrefs.dita#prod/productshortname"></ph> throws
-an error. <ph conref="refconrefs.dita#prod/productshortname"></ph> does not
+result set without using the XMLSERIALIZE operator, <ph conref="../conrefs.dita#prod/productshortname"></ph> throws
+an error. <ph conref="../conrefs.dita#prod/productshortname"></ph> does not
implicitly serialize XML values.</p></note></section>
<refsyn><title>Syntax</title><codeblock><b>XMLSERIALIZE ( <varname>xml-value-expression</varname> AS <varname>string-data-type</varname> )</b></codeblock
><dl><dlentry>
@@ -62,7 +62,7 @@
<dt><codeph>string-data-type</codeph></dt>
<dd>Must be a SQL character string type, such as CHAR, VARCHAR, LONG VARCHAR,
or CLOB. If you specify a type that is not a valid character string type, <ph
-conref="refconrefs.dita#prod/productshortname"></ph> throws an error.</dd>
+conref="../conrefs.dita#prod/productshortname"></ph> throws an error.</dd>
</dlentry></dl></refsyn>
<section><title>Examples</title><p>In the <codeph>x_table</codeph> table,
to display the contents of the <codeph>xcol</codeph> XML column, use this
@@ -77,7 +77,7 @@
PASSING BY REF <varname>xcol</varname> EMPTY ON EMPTY)
AS VARCHAR(50))
FROM <varname>x_table</varname></codeblock></p></section>
-<section><title>Usage note</title><p><ph conref="refconrefs.dita#prod/productshortname"></ph> requires
+<section><title>Usage note</title><p><ph conref="../conrefs.dita#prod/productshortname"></ph> requires
that a JAXP parser, such as Apache Xerces, and that Apache Xalan are listed
in the Java classpath for the XML functions to work. If either the JAXP parser
or Xalan is missing from the classpath, attempts to use the XMLSERIALIZE operator
Modified: db/derby/docs/trunk/src/ref/rrefgpc1.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefgpc1.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefgpc1.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefgpc1.dita Fri Mar 30 08:19:13 2007
@@ -24,12 +24,12 @@
<keywords><indexterm>java.sql.DatabaseMetaData.getProcedureColumns method</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> supports
-Java procedures. <ph conref="refconrefs.dita#prod/productshortname"></ph> allows
-you to call Java procedures within SQL statements. <ph conref="refconrefs.dita#prod/productshortname"></ph> returns
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
+Java procedures. <ph conref="../conrefs.dita#prod/productshortname"></ph> allows
+you to call Java procedures within SQL statements. <ph conref="../conrefs.dita#prod/productshortname"></ph> returns
information about the parameters in the <i>getProcedureColumns</i> call. If
the corresponding Java method is overloaded, it returns information about
-each signature separately. <ph conref="refconrefs.dita#prod/productshortname"></ph> returns
+each signature separately. <ph conref="../conrefs.dita#prod/productshortname"></ph> returns
information for all Java procedures defined by CREATE PROCEDURE.</p></section>
<section><p><i>getProcedureColumns</i> returns a <i>ResultSet</i>. Each row
describes a single parameter or return value.</p></section>
Modified: db/derby/docs/trunk/src/ref/rrefidentityvallocal.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefidentityvallocal.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefidentityvallocal.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefidentityvallocal.dita Fri Mar 30 08:19:13 2007
@@ -20,7 +20,7 @@
<reference id="rrefidentityvallocal" xml:lang="en-us">
<title>IDENTITY_VAL_LOCAL function</title>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> supports
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
the IDENTITY_VAL_LOCAL function. </p></section>
<section><p><b>Syntax:</b> <codeblock> IDENTITY_VAL_LOCAL ( )</codeblock></p></section>
<section><p>The IDENTITY_VAL_LOCAL function is a non-deterministic function
@@ -34,7 +34,7 @@
is the value assigned to the identity column of the table identified in the
most recent single row INSERT statement. The INSERT statement must contain
a VALUES clause on a table containing an identity column. The assigned value
-is an identity value generated by <ph conref="refconrefs.dita#prod/productshortname"></ph>.
+is an identity value generated by <ph conref="../conrefs.dita#prod/productshortname"></ph>.
The function returns a null value when a single row INSERT statement with
a VALUES clause has not been issued for a table containing an identity column.</p></section>
<section><p>The result of the function is not affected by the following:
Modified: db/derby/docs/trunk/src/ref/rrefidlengthlimits.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefidlengthlimits.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefidlengthlimits.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefidlengthlimits.dita Fri Mar 30 08:19:13 2007
@@ -21,7 +21,7 @@
<title>Limitations on identifier length </title>
<refbody>
<table frame="all"><title>Identifier length limitations</title><desc>The following
-table lists limitations on identifier lengths in <ph conref="refconrefs.dita#prod/productshortname"></ph>.</desc>
+table lists limitations on identifier lengths in <ph conref="../conrefs.dita#prod/productshortname"></ph>.</desc>
<tgroup cols="2" colsep="1" rowsep="1"><colspec colname="colspec0" colwidth="228*"/>
<colspec colname="colspec1" colwidth="228*"/>
<thead>
Modified: db/derby/docs/trunk/src/ref/rrefimportdataproc.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefimportdataproc.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefimportdataproc.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefimportdataproc.dita Fri Mar 30 08:19:13 2007
@@ -91,6 +91,6 @@
data fields from a delimited data file called <codeph>data.del</codeph> into
the <codeph>staff</codeph> table: <codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_DATA
(NULL, 'STAFF', null, '1,3,4', 'data.del', null, null, null,0)</codeblock></p></section>
-<section><p>For more information on importing, see the <i><ph conref="refconrefs.dita#pub/citutilities"></ph></i>.</p></section>
+<section><p>For more information on importing, see the <i><ph conref="../conrefs.dita#pub/citutilities"></ph></i>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefimportproc.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefimportproc.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefimportproc.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefimportproc.dita Fri Mar 30 08:19:13 2007
@@ -80,6 +80,6 @@
the percentage character (%) as the string delimiter, and a semicolon (;)
as the column delimiter: <codeblock>CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE
(null, 'STAFF', 'c:/output/myfile.del', ';', '%', null,0);</codeblock></p></section>
-<section><p>For more information on importing, see the <i><ph conref="refconrefs.dita#pub/citutilities"></ph></i>.</p></section>
+<section><p>For more information on importing, see the <i><ph conref="../conrefs.dita#pub/citutilities"></ph></i>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjavcallstatout.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjavcallstatout.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjavcallstatout.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjavcallstatout.dita Fri Mar 30 08:19:13 2007
@@ -25,7 +25,7 @@
</keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> supports
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
OUT parameters and CALL statements that return values, as in the following
example: <codeblock expanse="column"><b>CallableStatement cs = conn.prepareCall(
"? = CALL getDriverType(cast (? as INT))"
Modified: db/derby/docs/trunk/src/ref/rrefjavciro.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjavciro.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjavciro.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjavciro.dita Fri Mar 30 08:19:13 2007
@@ -28,7 +28,7 @@
DatabaseMetaData</i> value is returned. For example, <i>Connections</i> set
to read-only using the <i>setReadOnly</i> method, <i>Connections</i> for which
the user has been defined as a <i>readOnlyAccess</i> user (with one of the <ph
-conref="refconrefs.dita#prod/productshortname"></ph> properties), and <i>Connections</i> to
+conref="../conrefs.dita#prod/productshortname"></ph> properties), and <i>Connections</i> to
databases on read-only media return true.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjavcsro.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjavcsro.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjavcsro.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjavcsro.dita Fri Mar 30 08:19:13 2007
@@ -26,6 +26,6 @@
<refbody>
<section><p><i>java.sql.Connection.setReadOnly</i> is supported.</p><p>See
the section "Differences using the Connection.setReadOnly method" in
-the <ph conref="refconrefs.dita#pub/citadmin"></ph> for more information.</p></section>
+the <ph conref="../conrefs.dita#pub/citadmin"></ph> for more information.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjavcsti.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjavcsti.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjavcsti.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjavcsti.dita Fri Mar 30 08:19:13 2007
@@ -28,13 +28,13 @@
<refbody>
<section><p><i>java.sql.Connection.TRANSACTION_SERIALIZABLE</i>, <i>java.sql.Connection.TRANSACTION_REPEATABLE_READ</i>,
<i>java.sql.Connection.TRANSACTION_READ_COMMITTED, and </i><i>java.sql.Connection.TRANSACTION_READ_UNCOMMITTED</i> transaction
-isolations are available from a <ph conref="refconrefs.dita#prod/productshortname"></ph> database.</p></section>
+isolations are available from a <ph conref="../conrefs.dita#prod/productshortname"></ph> database.</p></section>
<section><p><i>TRANSACTION_READ_COMMITTED</i> is the default isolation level.</p></section>
<section><p>Changing the current isolation for the connection with <i>setTransactionIsolation</i> commits
the current transaction and begins a new transaction.
For more details about transaction isolation, see "Locking, concurrency, and
isolation" in the
-<cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
+<cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjavsaverestrict.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjavsaverestrict.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjavsaverestrict.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjavsaverestrict.dita Fri Mar 30 08:19:13 2007
@@ -21,9 +21,9 @@
<reference id="rrefjavsaverestrict" xml:lang="en-us">
<title>Restrictions on savepoints</title>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> does
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> does
not support savepoints within a trigger.</p></section>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> does
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> does
not release locks as part of the rollback to savepoint.
<table frame="all"><title>JDBC 3.0 Savepoint Methods <ph><indexterm>Savepoints<indexterm>methods</indexterm></indexterm></ph></title>
<tgroup cols="3" colsep="1" rowsep="1"><colspec colname="1" colnum="1" colwidth="12*"/>
Modified: db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjavsqlprst.dita Fri Mar 30 08:19:13 2007
@@ -32,7 +32,7 @@
passing in large amounts of data in smaller chunks. When the statement is
executed, the JDBC driver makes repeated calls to this input stream, reading
its contents and transmitting those contents as the parameter data.</p></section>
-<section><p><indexterm>setBinaryStream</indexterm><ph conref="refconrefs.dita#prod/productshortname"></ph> supports
+<section><p><indexterm>setBinaryStream</indexterm><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
the three types of streams that JDBC 1.2 provides. These three streams are:
<ul>
<li><i>setBinaryStream</i><indexterm>setBinaryStream</indexterm> <p>for streams
@@ -43,9 +43,9 @@
> <p>for streams containing Unicode characters</p></li>
</ul></p></section>
<section><p><indexterm>Stream</indexterm>JDBC 2.0 and JDBC 3.0 require that you specify the
-length of the stream and <ph conref="refconrefs.dita#prod/productshortname"></ph>
+length of the stream and <ph conref="../conrefs.dita#prod/productshortname"></ph>
enforces this requirement if your application runs on JDK 1.5 or earlier. If your application runs
-on JDK 1.6, then <ph conref="refconrefs.dita#prod/productshortname"></ph> exposes a JDBC
+on JDK 1.6, then <ph conref="../conrefs.dita#prod/productshortname"></ph> exposes a JDBC
4.0 implementation, which
lets you use the streaming interfaces without having to specify the
stream length.
Modified: db/derby/docs/trunk/src/ref/rrefjdbc1020262.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc1020262.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc1020262.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc1020262.dita Fri Mar 30 08:19:13 2007
@@ -33,7 +33,7 @@
<section><p>A JDBC escape clause begins and ends with curly braces. A keyword
always follows the opening curly brace:</p></section>
<example> <codeblock><b>{<b><i>keyword</i></b> }</b></codeblock></example>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> supports
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
the following JDBC escape keywords, which are case-insensitive: <ul>
<li><i><xref href="rrefjdbc70824.dita#rrefjdbc70824"></xref></i> <p>The escape keyword
for use in <i>CallableStatements</i>.</p></li>
@@ -50,7 +50,7 @@
<li><i><xref href="rrefjdbc41784.dita#rrefjdbc41784"></xref></i> <p>The escape keyword
for timestamp formats.</p></li>
</ul></p></section>
-<section><p>Other JDBC escape keywords are not supported. <note><ph conref="refconrefs.dita#prod/productshortname"></ph> returns
+<section><p>Other JDBC escape keywords are not supported. <note><ph conref="../conrefs.dita#prod/productshortname"></ph> returns
the SQL unchanged in the <i>Connection.nativeSQL</i> call, since the escape
syntax is native to SQL. In addition, it is unnecessary to call <i>Statement.setEscapeProcessing</i> for
this reason.</note></p></section>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc10889.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc10889.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc10889.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc10889.dita Fri Mar 30 08:19:13 2007
@@ -25,11 +25,11 @@
</metadata></prolog>
<refbody>
<section><p>You can supply an optional list of attributes to a database connection
-URL. <ph conref="refconrefs.dita#prod/productshortname"></ph> translates these
+URL. <ph conref="../conrefs.dita#prod/productshortname"></ph> translates these
attributes into properties, so you can also set attributes in a <i>Properties</i> object
passed to <i>DriverManager.getConnection</i>. (You cannot set those attributes
as system properties, only in an object passed to the <i>DriverManager.getConnection</i> method.)</p></section>
-<section><p>These attributes are specific to <ph conref="refconrefs.dita#prod/productshortname"></ph> and
+<section><p>These attributes are specific to <ph conref="../conrefs.dita#prod/productshortname"></ph> and
are listed in <xref href="rrefattrib24612.dita#rrefattrib24612"></xref>.</p></section>
<section><p><indexterm>Database connection URL<indexterm>settable through
Properties in connection call</indexterm></indexterm>Attribute name/value
@@ -50,8 +50,8 @@
"jdbc:derby:sampleDB", "dba", "password");</b></codeblock></p></section>
<section> <note>Attributes are not parsed for correctness. If you pass in
an incorrect attribute or corresponding value, it is simply ignored. (<ph
-conref="refconrefs.dita#prod/productshortname"></ph> does provide a tool for
+conref="../conrefs.dita#prod/productshortname"></ph> does provide a tool for
parsing the correctness of attributes. For more information, see the <cite><ph
-conref="refconrefs.dita#pub/citutilities"></ph></cite>.)</note></section>
+conref="../conrefs.dita#pub/citutilities"></ph></cite>.)</note></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc12124.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc12124.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc12124.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc12124.dita Fri Mar 30 08:19:13 2007
@@ -25,9 +25,9 @@
formats</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section> <p><ph conref="refconrefs.dita#prod/productshortname"></ph> interprets
+<section> <p><ph conref="../conrefs.dita#prod/productshortname"></ph> interprets
the JDBC escape syntax for time as equivalent to the correct SQL syntax for
-times. <ph conref="refconrefs.dita#prod/productshortname"></ph> also supports
+times. <ph conref="../conrefs.dita#prod/productshortname"></ph> also supports
the ISO format of 8 characters (6 digits, and 2 decimal points).</p></section>
<refsyn><title>Syntax</title><codeblock><b>{t 'hh:mm:ss'}</b></codeblock> </refsyn>
<section><title>Equivalent to</title><codeblock><b>TIME 'hh:mm:ss'</b></codeblock> </section>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc15905.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc15905.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc15905.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc15905.dita Fri Mar 30 08:19:13 2007
@@ -24,7 +24,7 @@
<keywords><indexterm>java.sql.DatabaseMetaData interface</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section><p>This section discusses <codeph>java.sql.DatabaseMetaData</codeph> functionality in <ph conref="refconrefs.dita#prod/productshortname"></ph>.
+<section><p>This section discusses <codeph>java.sql.DatabaseMetaData</codeph> functionality in <ph conref="../conrefs.dita#prod/productshortname"></ph>.
</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc16643.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc16643.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc16643.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc16643.dita Fri Mar 30 08:19:13 2007
@@ -25,15 +25,15 @@
<indexterm>SQLExceptions</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> supplies
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> supplies
values for the <i>getMessage()</i>, <i>getSQLState()</i>, and <i>getErrorCode()</i> calls
-of <i>SQLExceptions</i>. In addition, <ph conref="refconrefs.dita#prod/productshortname"></ph> sometimes
+of <i>SQLExceptions</i>. In addition, <ph conref="../conrefs.dita#prod/productshortname"></ph> sometimes
returns multiple <i>SQLExceptions</i> using the <i>nextException</i> chain.
The first exception is always the most severe exception, with SQL-92 Standard
-exceptions preceding those that are specific to <ph conref="refconrefs.dita#prod/productshortname"></ph>.
+exceptions preceding those that are specific to <ph conref="../conrefs.dita#prod/productshortname"></ph>.
For information on processing <i>SQLExceptions</i>, see "Working with <ph
-conref="refconrefs.dita#prod/productshortname"></ph> SQLExceptions in an application"
-in the <cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
+conref="../conrefs.dita#prod/productshortname"></ph> SQLExceptions in an application"
+in the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc20377.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc20377.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc20377.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc20377.dita Fri Mar 30 08:19:13 2007
@@ -139,8 +139,8 @@
these are stored as DOUBLE PRECISION values, and so always have the type code
DOUBLE when retrieved.</li>
<li id="sqlxml">SQLXML is only valid in JDBC 4.0 and later environments. SQLXML
-corresponds to the SQL type XML in <ph conref="refconrefs.dita#prod/productshortname"></ph>.
- However, <ph conref="refconrefs.dita#prod/productshortname"></ph> does not
+corresponds to the SQL type XML in <ph conref="../conrefs.dita#prod/productshortname"></ph>.
+ However, <ph conref="../conrefs.dita#prod/productshortname"></ph> does not
recognize the java.sql.Types.SQLXML data type and does not support any JDBC-side
operations for the XML data type. Support for XML and the related operators
is implemented only at the SQL layer. See <xref href="rrefsqljtypexml.dita#rrefsqljtypexml">XML
Modified: db/derby/docs/trunk/src/ref/rrefjdbc20485.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc20485.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc20485.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc20485.dita Fri Mar 30 08:19:13 2007
@@ -24,7 +24,7 @@
<keywords><indexterm>java.sql.CallableStatement interface</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> supports
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
all the JDBC 1.2 methods of <i>CallableStatement</i>: <ul>
<li><i>getBoolean()</i></li>
<li><i>getByte()</i></li>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc23502.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc23502.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc23502.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc23502.dita Fri Mar 30 08:19:13 2007
@@ -30,10 +30,10 @@
positioned updates and deletes to operate against the row the underlying cursor
is on, and not the current row of the <i>ResultSet</i>.<indexterm>Cursors<indexterm>pre-fetching
affecting</indexterm></indexterm></p></section>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> provides
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
all the required JDBC 1.2 type conversions of the <i>getXXX</i> methods.</p></section>
<section><p>JDBC does not define the sort of rounding to use for <i>ResultSet.getBigDecimal</i>. <ph
-conref="refconrefs.dita#prod/productshortname"></ph> uses <i>java.math.BigDecimal.ROUND_HALF_DOWN</i>.</p></section>
+conref="../conrefs.dita#prod/productshortname"></ph> uses <i>java.math.BigDecimal.ROUND_HALF_DOWN</i>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc27433.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc27433.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc27433.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc27433.dita Fri Mar 30 08:19:13 2007
@@ -25,12 +25,12 @@
<keywords><indexterm>Database connection URL</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section><p>A <ph conref="refconrefs.dita#prod/productshortname"></ph> database
+<section><p>A <ph conref="../conrefs.dita#prod/productshortname"></ph> database
connection URL consists of the basic database connection URL followed by an
optional subsubprotocol and optional attributes.</p></section>
<section><p>This section provides reference information only. For a more complete
description, including examples, see "Connecting to Databases" in Chapter
-1 of the <cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
+1 of the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc27734.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc27734.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc27734.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc27734.dita Fri Mar 30 08:19:13 2007
@@ -26,7 +26,7 @@
</keywords>
</metadata></prolog>
<refbody>
-<section><p>A <ph conref="refconrefs.dita#prod/productshortname"></ph> <i>Connection</i> object
+<section><p>A <ph conref="../conrefs.dita#prod/productshortname"></ph> <i>Connection</i> object
is not garbage-collected until all other JDBC objects created from that connection
are explicitly closed or are themselves garbage-collected. Once the connection
is closed, no further JDBC requests can be made against objects created from
@@ -35,7 +35,7 @@
collection of</indexterm></indexterm></p></section>
<section><p>A session-severity or higher exception causes the connection to
close and all other JDBC objects against it to be closed. System-severity
-exceptions cause the <ph conref="refconrefs.dita#prod/productshortname"></ph> system
+exceptions cause the <ph conref="../conrefs.dita#prod/productshortname"></ph> system
to shut down, which not only closes the connection but means that no new connections
should be created in the current JVM.</p></section>
</refbody>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc27768.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc27768.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc27768.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc27768.dita Fri Mar 30 08:19:13 2007
@@ -26,7 +26,7 @@
</keywords>
</metadata></prolog>
<refbody>
-<section> <p><ph conref="refconrefs.dita#prod/productshortname"></ph> interprets
+<section> <p><ph conref="../conrefs.dita#prod/productshortname"></ph> interprets
the JDBC escape syntax for date as equivalent to the SQL syntax for dates.</p></section>
<refsyn><title>Syntax</title><codeblock><b>{d 'yyyy-mm-dd'}</b></codeblock> </refsyn>
<section><title>Equivalent to</title><codeblock><b>DATE('yyyy-mm-dd')</b></codeblock> </section>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc29874.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc29874.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc29874.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc29874.dita Fri Mar 30 08:19:13 2007
@@ -24,7 +24,7 @@
<keywords><indexterm>java.sql.PreparedStatement interface</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> provides
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> provides
all the required JDBC 1.2 type conversions and additionally allows use of
the individual <i>setXXX</i> methods for each type as if a <i>setObject(Value,
JDBCTypeCode)</i> invocation were made. </p></section>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc2_0summary.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc2_0summary.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc2_0summary.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc2_0summary.dita Fri Mar 30 08:19:13 2007
@@ -29,7 +29,7 @@
<section>
<p>
This section documents the methods available since JDBC 2.0 that are supported
-by <ph conref="refconrefs.dita#prod/productshortname"></ph>.
+by <ph conref="../conrefs.dita#prod/productshortname"></ph>.
</p>
</section>
</refbody>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc30469.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc30469.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc30469.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc30469.dita Fri Mar 30 08:19:13 2007
@@ -24,12 +24,12 @@
<keywords><indexterm>java.sql.SQLWarning class</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> can generate
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> can generate
a warning in certain circumstances. A warning is generated if, for example,
you try to connect to a database with the <i>create</i> attribute set to <i>true</i> if
the database already exists. Aggregates like sum() also raise a warning if
NULL values are encountered during the evaluation.</p></section>
-<section><p>All other informational messages are written to the <ph conref="refconrefs.dita#prod/productshortname"></ph> system's <i>derby.log</i
+<section><p>All other informational messages are written to the <ph conref="../conrefs.dita#prod/productshortname"></ph> system's <i>derby.log</i
> file.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc32052.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc32052.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc32052.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc32052.dita Fri Mar 30 08:19:13 2007
@@ -24,7 +24,7 @@
</keywords>
</metadata></prolog>
<refbody>
-<section><p>The class that loads <ph conref="refconrefs.dita#prod/productshortname"></ph>'s
+<section><p>The class that loads <ph conref="../conrefs.dita#prod/productshortname"></ph>'s
local JDBC driver is the class <i>org.apache.derby.jdbc.EmbeddedDriver</i>.
Listed below are some of the ways to create instances of that class. Do not use the class directly through the <i>java.sql.Driver</i> interface.
Use the <i>DriverManager</i> class to create connections. <ul id="i1012571">
@@ -51,10 +51,10 @@
applicationClass</b></codeblock></example>
<section><p>The actual driver that gets registered in the <i>DriverManager</i> to
handle the <i>jdbc:derby:</i> protocol is not the class <i>org.apache.derby.jdbc.EmbeddedDriver</i>;
-that class simply detects the type of <ph conref="refconrefs.dita#prod/productshortname"></ph> driver
-needed and then causes the appropriate <ph conref="refconrefs.dita#prod/productshortname"></ph> driver
+that class simply detects the type of <ph conref="../conrefs.dita#prod/productshortname"></ph> driver
+needed and then causes the appropriate <ph conref="../conrefs.dita#prod/productshortname"></ph> driver
to be loaded.</p></section>
-<section><p>The only supported way to connect to a <ph conref="refconrefs.dita#prod/productshortname"></ph> system
+<section><p>The only supported way to connect to a <ph conref="../conrefs.dita#prod/productshortname"></ph> system
through the <i>jdbc:derby:</i> protocol is using the <i>DriverManager</i> to
obtain a driver (<i>java.sql.Driver</i>) or connection (<i>java.sql.Connection</i>)
through the <i>getDriver</i> and <i>getConnection</i> method calls.</p></section>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc32593.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc32593.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc32593.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc32593.dita Fri Mar 30 08:19:13 2007
@@ -26,7 +26,7 @@
</metadata></prolog>
<refbody>
<section><p>JDBC 3.0 adds some functionality to the core API. This section
-documents the features supported by <ph conref="refconrefs.dita#prod/productshortname"></ph>.
+documents the features supported by <ph conref="../conrefs.dita#prod/productshortname"></ph>.
<note>These features are present only in a Java 2 version 1.4 or higher
environment.</note></p></section>
<section><p>These features are: <ul>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc34565.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc34565.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc34565.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc34565.dita Fri Mar 30 08:19:13 2007
@@ -35,13 +35,13 @@
to set database connection URL attributes.</p></section>
<section><p><indexterm>Schemas<indexterm>APP as default</indexterm></indexterm>You
can also supply strings representing user names and passwords. When they are
-supplied, <ph conref="refconrefs.dita#prod/productshortname"></ph> checks
+supplied, <ph conref="../conrefs.dita#prod/productshortname"></ph> checks
whether they are valid for the current system if user authentication is enabled.
-User names are passed to <ph conref="refconrefs.dita#prod/productshortname"></ph> as
+User names are passed to <ph conref="../conrefs.dita#prod/productshortname"></ph> as
authorization identifiers, which are used to determine whether the user is
authorized for access to the database and for determining the default schema.
-When the connection is established, if no user is supplied, <ph conref="refconrefs.dita#prod/productshortname"></ph> sets
-the default user to <i>APP</i>, which <ph conref="refconrefs.dita#prod/productshortname"></ph> uses
+When the connection is established, if no user is supplied, <ph conref="../conrefs.dita#prod/productshortname"></ph> sets
+the default user to <i>APP</i>, which <ph conref="../conrefs.dita#prod/productshortname"></ph> uses
to name the default schema. If a user is supplied, the default schema is the
same as the user name.</p></section>
</refbody>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc34954.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc34954.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc34954.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc34954.dita Fri Mar 30 08:19:13 2007
@@ -31,12 +31,12 @@
<section><p>Do not request it from <i>org.apache.derby.jdbc.EmbeddedDriver</i>,
which is only an intermediary class that loads the actual driver.</p></section>
<section><p>This method might return a <i>DriverPropertyInfo</i> object. In
-a <ph conref="refconrefs.dita#prod/productshortname"></ph> system, it consists
+a <ph conref="../conrefs.dita#prod/productshortname"></ph> system, it consists
of an array of database connection URL attributes. The most useful attribute
is <i><xref href="rrefattrib17246.dita#rrefattrib17246">databaseName=nameofDatabase</xref>,</i> which
means that the object consists of a list of booted databases in the current
system.</p></section>
-<section><p>For example, if a <ph conref="refconrefs.dita#prod/productshortname"></ph> system
+<section><p>For example, if a <ph conref="../conrefs.dita#prod/productshortname"></ph> system
has the databases <i>toursDB</i> and <i>flightsDB</i> in its system directory,
all the databases in the system are set to boot automatically, and a user
has also connected to a database <filepath>A:/dbs/tours94</filepath>, the
@@ -48,7 +48,7 @@
name (in any form) or include the shutdown attribute with the value true.</p></section>
<section><p>For more information about <i>java.sql.Driver.getPropertyInfo</i>,
see "Offering connection choices to the user" in the <cite><ph
-conref="refconrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
+conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc37244.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc37244.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc37244.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc37244.dita Fri Mar 30 08:19:13 2007
@@ -26,7 +26,7 @@
for</indexterm></indexterm></keywords>
</metadata></prolog>
<refbody>
-<section> <p><ph conref="refconrefs.dita#prod/productshortname"></ph> interprets
+<section> <p><ph conref="../conrefs.dita#prod/productshortname"></ph> interprets
the JDBC escape syntax for outer joins (and all join operations) as equivalent
to the correct SQL syntax for outer joins or the appropriate join operation.</p> <p>For
information about join operations, see <xref href="rrefsqlj29840.dita#rrefsqlj29840"></xref>.</p></section>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc37352.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc37352.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc37352.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc37352.dita Fri Mar 30 08:19:13 2007
@@ -29,11 +29,11 @@
connection URL is <codeblock><b>jdbc:derby: [<b><i>subsubprotocol:</i></b>][<i>databasename</i>][;<b><i>attributes</i></b>]*</b></codeblock><ul
id="i1025762">
<li><i id="jdbc31337">jdbc:derby:</i> <p>In JDBC lingo, <i>derby</i> is
-the <i>subprotocol</i> for connecting to a <ph conref="refconrefs.dita#prod/productshortname"></ph> database.
+the <i>subprotocol</i> for connecting to a <ph conref="../conrefs.dita#prod/productshortname"></ph> database.
The subprotocol is always <i>derby</i> and does not vary.</p></li>
<li><i>subsubprotocol:<ph><indexterm>Subsubprotocol<indexterm>part of database
connection URL syntax</indexterm></indexterm></ph></i> <p><i>subsubprotocol</i>,
-which is not typically specified, specifies where <ph conref="refconrefs.dita#prod/productshortname"></ph> looks
+which is not typically specified, specifies where <ph conref="../conrefs.dita#prod/productshortname"></ph> looks
for a database: in a directory, in a classpath, or in a jar file. It is used
only in rare instances, usually for read-only databases. <i>subsubprotocol</i> is
one of the following:</p><ul>
@@ -47,12 +47,12 @@
</ul><p>jar: requires an additional element immediately before the <i>databaseName</i>:
<codeblock><b><i>(<i>pathToArchive</i>)</i></b></codeblock></p><p><i>pathToArchive</i> is
the path to the jar or zip file that holds the database and includes the name
-of the jar or zip file.</p><p>See the <cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite> for
+of the jar or zip file.</p><p>See the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite> for
examples of database connection URLs for read-only databases.</p></li>
<li><i>databaseName</i> <p>Specify the <i>databaseName</i> to connect to
an existing database or a new one. </p> <p>You can specify the database name
alone, or with a relative or absolute path. See "Standard Connections-Connecting
-to Databases in the File System" in Chapter 1 of the <cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite>.</p></li>
+to Databases in the File System" in Chapter 1 of the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</p></li>
<li><i>attributes</i> <p>Specify 0 or more database connection URL attributes
as detailed in <xref href="rrefjdbc10889.dita#rrefjdbc10889"></xref>.</p></li>
</ul></p></section>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc38274.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc38274.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc38274.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc38274.dita Fri Mar 30 08:19:13 2007
@@ -23,7 +23,7 @@
<keywords><indexterm>java.sql.ResultSetMetaData interface</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> does
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> does
not track the source or updatability of columns in <i>ResultSets</i>, and
so always returns the following constants for the following methods: <table
pgwide="0" frame="all">
Modified: db/derby/docs/trunk/src/ref/rrefjdbc40794.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc40794.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc40794.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc40794.dita Fri Mar 30 08:19:13 2007
@@ -23,7 +23,7 @@
<keywords><indexterm>java.sql.Statement interface</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> does
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> does
not implement the JDBC 1.2 <i>setEscapeProcessing</i> method of <i>java.sql.Statement</i>.
In addition, the following optional methods raise "Feature not
supported" exceptions:
Modified: db/derby/docs/trunk/src/ref/rrefjdbc41784.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc41784.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc41784.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc41784.dita Fri Mar 30 08:19:13 2007
@@ -26,9 +26,9 @@
syntax for</indexterm></indexterm></keywords>
</metadata></prolog>
<refbody>
-<section> <p><ph conref="refconrefs.dita#prod/productshortname"></ph> interprets
+<section> <p><ph conref="../conrefs.dita#prod/productshortname"></ph> interprets
the JDBC escape syntax for timestamp as equivalent to the correct SQL syntax
-for timestamps. <ph conref="refconrefs.dita#prod/productshortname"></ph> also
+for timestamps. <ph conref="../conrefs.dita#prod/productshortname"></ph> also
supports the ISO format of 23 characters (17 digits, 3 dashes, and 3 decimal
points).</p></section>
<refsyn><title>Syntax</title> <codeblock><b>{ts 'yyyy-mm-dd hh:mm:ss.f...'}</b></codeblock> </refsyn>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc4_0dataSource.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc4_0dataSource.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc4_0dataSource.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc4_0dataSource.dita Fri Mar 30 08:19:13 2007
@@ -33,7 +33,7 @@
iterating through a table. You use this mechanism by passing an
annotated query to your DataSource's <i>createQueryObject</i> method.
To expose this <i>createQueryObject</i> method,
-<ph conref="refconrefs.dita#prod/productshortname"></ph>
+<ph conref="../conrefs.dita#prod/productshortname"></ph>
adds new JDBC 4.0-specific DataSources. Use these DataSources if your
application runs on JDK 1.6 or higher.
</p>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc4_0databaseMetaData.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc4_0databaseMetaData.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc4_0databaseMetaData.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc4_0databaseMetaData.dita Fri Mar 30 08:19:13 2007
@@ -32,7 +32,7 @@
<refbody>
<section>
<p>
-<ph conref="refconrefs.dita#prod/productshortname"></ph>
+<ph conref="../conrefs.dita#prod/productshortname"></ph>
implements all of the new metadata methods added by JDBC 4.0.
</p>
<ul>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc4_0sqlexception.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc4_0sqlexception.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc4_0sqlexception.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc4_0sqlexception.dita Fri Mar 30 08:19:13 2007
@@ -28,7 +28,7 @@
<section>
<p>
If your application runs on JDK 1.6 or higher, exceptions raised by
-<ph conref="refconrefs.dita#prod/productshortname"></ph>
+<ph conref="../conrefs.dita#prod/productshortname"></ph>
will generally be one of the refined subclasses of SQLException,
introduced by JDBC 4.0. These refined exceptions are raised under the
conditions described by their respective javadoc.
Modified: db/derby/docs/trunk/src/ref/rrefjdbc4_0statement.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc4_0statement.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc4_0statement.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc4_0statement.dita Fri Mar 30 08:19:13 2007
@@ -29,7 +29,7 @@
<refbody>
<section>
<p>
-<ph conref="refconrefs.dita#prod/productshortname"></ph>'s
+<ph conref="../conrefs.dita#prod/productshortname"></ph>'s
Statements implement the following new metadata methods added by JDBC 4.0.
</p>
<ul>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc4_0summary.dita Fri Mar 30 08:19:13 2007
@@ -36,7 +36,7 @@
<section>
<p>
JDBC 4.0 adds some functionality to the core API. This section
-documents the features supported by <ph conref="refconrefs.dita#prod/productshortname"></ph>.
+documents the features supported by <ph conref="../conrefs.dita#prod/productshortname"></ph>.
</p>
<p><note>These features are present only in a JDK 1.6 or higher
environment.
@@ -45,7 +45,7 @@
<section><p>These features are:</p>
<ul>
<li><b>DataSources.</b> To support the JDBC 4.0 ease of development,
-<ph conref="refconrefs.dita#prod/productshortname"></ph>
+<ph conref="../conrefs.dita#prod/productshortname"></ph>
introduces new implementations of <codeph>javax.sql.DataSource</codeph>. See
<xref href="rrefjdbc4_0dataSource.dita#rrefjdbc4_0dataSource"></xref>.
</li>
@@ -60,9 +60,9 @@
objects. This is a formal mechanism by which application servers can
look for vendor-specific extensions inside standard JDBC objects like
Connections, Statements, and ResultSets. For
-<ph conref="refconrefs.dita#prod/productshortname"></ph>,
+<ph conref="../conrefs.dita#prod/productshortname"></ph>,
this is a vacuous exercise because
-<ph conref="refconrefs.dita#prod/productshortname"></ph>
+<ph conref="../conrefs.dita#prod/productshortname"></ph>
does not expose any of these extensions.</li>
<li><b>Statement events.</b> With JDBC 4.0, Connection pools can listen for Statement closing and Statement error events. New methods were added to <i>javax.sql.PooledConnection</i>: <i>addStatementEventListener</i> and <i>removeStatementEventListener</i>.</li>
<li><b>Streaming APIs.</b> JDBC 4.0 adds new overloads of the streaming methods in CallableStatement, PreparedStatement, and ResultSet. These are the <i>setXXX</i> and <i>updateXXX</i> methods which take <i>java.io.InputStream</i> and <i>java.io.Reader</i> arguments. The new overloads allow you to omit the length arguments or to specify <i>long</i> lengths.</li>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc66688.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc66688.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc66688.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc66688.dita Fri Mar 30 08:19:13 2007
@@ -21,7 +21,7 @@
<reference id="rrefjdbc66688" xml:lang="en-us">
<title>java.sql.DatabaseMetaData interface: supported JDBC 2.0 methods</title>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> implements
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> implements
all of the JDBC 2.0 methods for this interface.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc71949.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc71949.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc71949.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc71949.dita Fri Mar 30 08:19:13 2007
@@ -21,7 +21,7 @@
<reference id="rrefjdbc71949" xml:lang="en-us">
<title>java.sql.ResultSetMetaData interface: supported JDBC 2.0 methods</title>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> implements
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> implements
all of the JDBC 2.0 methods for this interface.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc75719.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc75719.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc75719.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc75719.dita Fri Mar 30 08:19:13 2007
@@ -40,7 +40,7 @@
of <codeph>ints</codeph>. Here is sample source code for that method: <codeblock
expanse="column"><b>public static void doubleMyInt(int[] i) {
i[0] *=2;
- <ph>/* <ph conref="refconrefs.dita#prod/productshortname"></ph> returns the first element of the array.*/</ph>
+ <ph>/* <ph conref="../conrefs.dita#prod/productshortname"></ph> returns the first element of the array.*/</ph>
}</b></codeblock> <note>The return value is <i>not</i> wrapped in an array
even though the parameter to the method is.</note> <table frame="all"><title>INOUT
Parameter Type Correspondence</title>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc80004.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc80004.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc80004.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc80004.dita Fri Mar 30 08:19:13 2007
@@ -54,7 +54,7 @@
</table>
<section><title>Implementation notes</title><i>ResultSet.TYPE_FORWARD_ONLY</i> and <i>ResultSet.TYPE_SCROLL_INSENSITIVE</i> are
the only result set types supported. If you request <i>TYPE_SCROLL_SENSITIVE</i>, <ph
-conref="refconrefs.dita#prod/productshortname"></ph> issues an <i>SQLWarning</i> and
+conref="../conrefs.dita#prod/productshortname"></ph> issues an <i>SQLWarning</i> and
returns a <i>TYPE_SCROLL_INSENSITIVE ResultSet</i>. <p> These methods support
both <i>ResultSet.CONCUR_READ_ONLY</i> and <i>ResultSet.CONCUR_UPDATABLE</i> concurrencies. </p></section>
</refbody>
Modified: db/derby/docs/trunk/src/ref/rrefjdbc96386.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbc96386.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbc96386.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbc96386.dita Fri Mar 30 08:19:13 2007
@@ -29,18 +29,18 @@
(binary large object) type; <i>java.sql.Clob</i> is the mapping for the SQL
CLOB (character large object) type.</p></section>
<section><p>java.sql.Blob and java.sql.Clob provide a logical pointer to the
-large object rather than a complete copy of the objects. <ph conref="refconrefs.dita#prod/productshortname"></ph> processes
+large object rather than a complete copy of the objects. <ph conref="../conrefs.dita#prod/productshortname"></ph> processes
only one data page into memory at a time. The whole BLOB does not need to
be processed and stored in memory just to access the first few bytes of the
LOB object</p></section>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> now supports
-the built-in BLOB or CLOB data types. <ph conref="refconrefs.dita#prod/productshortname"></ph> also
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> now supports
+the built-in BLOB or CLOB data types. <ph conref="../conrefs.dita#prod/productshortname"></ph> also
provides the following support for these data types: <ul>
-<li><b>BLOB Features</b> <ph conref="refconrefs.dita#prod/productshortname"></ph> supports
+<li><b>BLOB Features</b> <ph conref="../conrefs.dita#prod/productshortname"></ph> supports
the <i>java.sql.Blob</i> interface and the BLOB-related methods listed in <i><xref
href="rrefjdbc99392.dita#rrefjdbc99392"></xref></i> and <i><xref href="rrefjdbc77156.dita#rrefjdbc77156"></xref></i>.
The <i>getBlob</i> methods of <i>CallableStatement</i> are not implemented.</li>
-<li><b>CLOB Features</b> <ph conref="refconrefs.dita#prod/productshortname"></ph> supports
+<li><b>CLOB Features</b> <ph conref="../conrefs.dita#prod/productshortname"></ph> supports
the java.sql.Clob interface and the CLOB-related methods listed in <i><xref href="rrefjdbc99392.dita#rrefjdbc99392"></xref></i> and <i><xref
href="rrefjdbc77156.dita#rrefjdbc77156"></xref></i>. The <i>getClob</i> methods
of <i>CallableStatement</i> procedures are not implemented.</li>
@@ -56,11 +56,11 @@
</ul></p></section>
<section><p>In addition, casting between strings and BLOBs is not recommended
because casting is platform and database dependent. </p></section>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> uses
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> uses
unicode strings (2 byte characters), while other database products may use
ASCII characters (1 byte per character). If various codepages are used, each
character might need several bytes. A larger BLOB type might be necessary
-to accommodate a normal string in <ph conref="refconrefs.dita#prod/productshortname"></ph>.
+to accommodate a normal string in <ph conref="../conrefs.dita#prod/productshortname"></ph>.
You should use CLOB types for storing strings. </p></section>
<section><p><b>Restrictions on BLOB, CLOB, (LOB-types):</b> <ul>
<li>LOB-types cannot be compared for equality(=) and non-equality(!=, <>. </li>
@@ -70,7 +70,7 @@
<li>DISTINCT, GROUP BY, ORDER BY clauses are also prohibited on LOB-types. </li>
<li>LOB-types cannot be involved in implicit casting as other base-types.</li>
</ul></p></section>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> implements
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> implements
all of the methods for these JDBC 2.0 interfaces except for the set and get
methods in <i>CallableStatement</i> interface.</p></section>
<section><p><b>Recommendations:</b> Because the lifespan of a <i>java.sql.Blob</i> or <i>java.sql.Clob</i> ends
Modified: db/derby/docs/trunk/src/ref/rrefjdbcescapedate.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbcescapedate.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbcescapedate.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbcescapedate.dita Fri Mar 30 08:19:13 2007
@@ -25,7 +25,7 @@
formats</indexterm></keywords>
</metadata></prolog>
<refbody>
-<section> <p><ph conref="refconrefs.dita#prod/productshortname"></ph> interprets
+<section> <p><ph conref="../conrefs.dita#prod/productshortname"></ph> interprets
the JDBC escape syntax for dates as equivalent to the correct SQL syntax for
dates.</p></section>
<refsyn><title>Syntax</title><codeblock><b>{d 'yyyy-mm-dd'}</b></codeblock> </refsyn>
Modified: db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbcjsr169.dita Fri Mar 30 08:19:13 2007
@@ -25,16 +25,16 @@
</keywords>
</metadata></prolog>
<refbody>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> supports
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> supports
the JDBC API defined for the Connected Device Configuration/Foundation Profile,
also known as JSR169. The features supported are a subset of the JDBC 3.0
-specification. Support for JSR169 is limited to the embedded driver. <ph conref="refconrefs.dita#prod/productshortname"></ph> does
+specification. Support for JSR169 is limited to the embedded driver. <ph conref="../conrefs.dita#prod/productshortname"></ph> does
not support using the Network Server under JSR169.</p></section>
<section><p>To obtain a connection under JSR169 specifications, use the <codeph>org.apache.derby.jdbc.EmbeddedSimpleDataSource</codeph> class.
This class is identical in implementation to the <codeph>org.apache.derby.jdbc.EmbeddedDataSource</codeph> class.
-See the <ph conref="refconrefs.dita#pub/citdevelop"></ph> for information
+See the <ph conref="../conrefs.dita#pub/citdevelop"></ph> for information
on using the properties of the <codeph>org.apache.derby.jdbc.EmbeddedDataSource</codeph> class.</p><p>Some
-other features to note concerning the JSR169 implementation using <ph conref="refconrefs.dita#prod/productshortname"></ph>:<ul>
+other features to note concerning the JSR169 implementation using <ph conref="../conrefs.dita#prod/productshortname"></ph>:<ul>
<li>Applications must get and set <codeph>DECIMAL</codeph> values using alternate
JDBC <codeph>getXXX</codeph> and <codeph>setXXX</codeph> methods, such as <codeph>getString()</codeph> and <codeph>setString()</codeph>.
Any alternate method that works against a DECIMAL type with JDBC 2.0 or 3.0
Modified: db/derby/docs/trunk/src/ref/rrefjdbcrefsqlxml.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjdbcrefsqlxml.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjdbcrefsqlxml.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjdbcrefsqlxml.dita Fri Mar 30 08:19:13 2007
@@ -25,14 +25,14 @@
</metadata></prolog>
<refbody>
<section><p>In JDBC 4.0, java.sql.SQLXML is the mapping for the SQL XML data
-type. However, <ph conref="refconrefs.dita#prod/productshortname"></ph> defines
+type. However, <ph conref="../conrefs.dita#prod/productshortname"></ph> defines
the XML data type and operators only in the SQL layer. There is no JDBC-side
support for the XML data type and operators</p><p>You cannot instantiate a
-java.sql.SQLXML object in <ph conref="refconrefs.dita#prod/productshortname"></ph>,
+java.sql.SQLXML object in <ph conref="../conrefs.dita#prod/productshortname"></ph>,
or bind directly into an XML value or retrieve an XML value directly from
a result set. You must bind and retrieve the XML data as Java strings or
character streams by explicitly specifying the XML operators, XMLPARSE and
-XMLSERIALIZE, as part of your SQL queries. </p><p>Additionally, <ph conref="refconrefs.dita#prod/productshortname"></ph> does
+XMLSERIALIZE, as part of your SQL queries. </p><p>Additionally, <ph conref="../conrefs.dita#prod/productshortname"></ph> does
not provide JDBC metatadata support for the XML data type. </p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjta16677.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjta16677.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjta16677.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjta16677.dita Fri Mar 30 08:19:13 2007
@@ -26,11 +26,11 @@
</metadata></prolog>
<refbody>
<section><p>J2EE, or the Java 2 Platform, Enterprise Edition, is a standard for development of enterprise applications based on reusable components in a multi-tier environment. In addition to the features of the Java 2 Platform, Standard Edition (J2SE) J2EE adds support for Enterprise Java Beans (EJBs), Java Server Pages (JSPs), Servlets, XML and many more. The J2EE architecture is used to bring together existing technologies and enterprise applications in a single, manageable environment.</p></section>
-<section><p><ph conref="refconrefs.dita#prod/productshortname"></ph> is a
+<section><p><ph conref="../conrefs.dita#prod/productshortname"></ph> is a
J2EE-conformant component in a distributed J2EE system. As such, it is one
part of a larger system that includes, among other things, a JNDI server,
a connection pool module, a transaction manager, a resource manager, and user
-applications. Within this system, <ph conref="refconrefs.dita#prod/productshortname"></ph> can
+applications. Within this system, <ph conref="../conrefs.dita#prod/productshortname"></ph> can
serve as the resource manager.</p></section>
<section><p>For more information on J2EE, see the J2EE specification available
at <i><xref format="html" href="http://java.sun.com/j2ee/docs.html" scope="local">http://java.sun.com/j2ee/docs.html</xref></i>.</p></section>
@@ -41,7 +41,7 @@
URLs. Implementation of one of the JDBC extensions, <i><xref href="rrefjta18596.dita#rrefjta18596/jta20722">javax.sql.DataSource</xref>,</i> provides
this support.</p></li>
<li>Connection pooling <p>A mechanism by which a connection pool server keeps
-a set of open connections to a resource manager (<ph conref="refconrefs.dita#prod/productshortname"></ph>).
+a set of open connections to a resource manager (<ph conref="../conrefs.dita#prod/productshortname"></ph>).
A user requesting a connection can get one of the available connections from
the pool. Such a connection pool is useful in client/server environments because
establishing a connection is relatively expensive. In an embedded environment,
@@ -66,8 +66,8 @@
<section><p>With the exception of the core JDBC interfaces, these interfaces
are not visible to the end-user application; instead, they are used only by
the other back-end components in the system. <note>For information on the
-classes that implement these interfaces and how to use <ph conref="refconrefs.dita#prod/productshortname"></ph> as
-a resource manager, see Chapter 6, "Using <ph conref="refconrefs.dita#prod/productshortname"></ph> as
-a J2EE Resource Manager" in the <cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite>.</note></p></section>
+classes that implement these interfaces and how to use <ph conref="../conrefs.dita#prod/productshortname"></ph> as
+a resource manager, see Chapter 6, "Using <ph conref="../conrefs.dita#prod/productshortname"></ph> as
+a J2EE Resource Manager" in the <cite><ph conref="../conrefs.dita#pub/citdevelop"></ph></cite>.</note></p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefjta18596.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjta18596.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjta18596.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjta18596.dita Fri Mar 30 08:19:13 2007
@@ -30,12 +30,12 @@
</keywords>
</metadata></prolog>
<refbody>
-<section><p>This section documents the JDBC extensions that <ph conref="refconrefs.dita#prod/productshortname"></ph> implements
+<section><p>This section documents the JDBC extensions that <ph conref="../conrefs.dita#prod/productshortname"></ph> implements
for J2EE compliance. (For more details about these extensions, see the API documentation for your version of the Java Development Kit, which you can find at <xref format="html"
href="http://java.sun.com/javase/reference/api.jsp"
scope="external"><i>http://java.sun.com/javase/reference/api.jsp</i></xref>).
<ul id="i1017905">
-<li><i id="jta20722">javax.sql.DataSource</i> <p><ph conref="refconrefs.dita#prod/productshortname"></ph>'s
+<li><i id="jta20722">javax.sql.DataSource</i> <p><ph conref="../conrefs.dita#prod/productshortname"></ph>'s
implementation of <i>DataSource</i> means that it supports JNDI; as a resource
manager, it allows a database to be named and registered within a JNDI server.
This allows the calling application to access the database by a name (as a
@@ -44,10 +44,10 @@
<p>Establishing a connection to the database can be a relatively expensive
operation in client/server environments. Establishing the connection once
and then using the same connection for multiple requests can dramatically
-improve the performance of a database.</p> <p>The <ph conref="refconrefs.dita#prod/productshortname"></ph> implementation
+improve the performance of a database.</p> <p>The <ph conref="../conrefs.dita#prod/productshortname"></ph> implementation
of <codeph>ConnectionPoolDataSource</codeph> and <codeph>PooledConnection</codeph> allows
a connection pool server to maintain a set of such connections to the resource
-manager (<ph conref="refconrefs.dita#prod/productshortname"></ph>). In an
+manager (<ph conref="../conrefs.dita#prod/productshortname"></ph>). In an
embedded environment, connections are much cheaper and connection pooling
is not necessary.</p></li>
<li id="i1018049"><i id="jta18170">javax.sql.XAConnection</i> <p>An <i>XAConnection</i> produces
@@ -56,9 +56,9 @@
<li id="i1018057"><i id="jta88962">javax.sql.XADataSource</i> <p>An <i>XADataSource</i> is
simply a <i>ConnectionPoolDataSource</i> that produces <i>XAConnections</i>.</p></li>
</ul></p></section>
-<section><p>In addition, <ph conref="refconrefs.dita#prod/productshortname"></ph> provides
+<section><p>In addition, <ph conref="../conrefs.dita#prod/productshortname"></ph> provides
three methods for <i>XADataSource, DataSource, and ConnectionPoolDataSource</i>. <ph
-conref="refconrefs.dita#prod/productshortname"></ph> supports a number of
+conref="../conrefs.dita#prod/productshortname"></ph> supports a number of
additional data source properties: <ul>
<li><i><ph></ph>setCreateDatabase(String create)</i> <p>Sets a property
to create a database at the next connection. The string argument must be "create".</p></li>
Modified: db/derby/docs/trunk/src/ref/rrefjta51021.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjta51021.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjta51021.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjta51021.dita Fri Mar 30 08:19:13 2007
@@ -25,7 +25,7 @@
</metadata></prolog>
<refbody>
<section><p>The JTA API is made up of the two interfaces and one exception
-that are part of the<i> java.transaction.xa</i> package. <ph conref="refconrefs.dita#prod/productshortname"></ph> fully
+that are part of the<i> java.transaction.xa</i> package. <ph conref="../conrefs.dita#prod/productshortname"></ph> fully
implements this API. <ul id="i1017757">
<li><i id="jta18387"><ph><indexterm>javax.transaction.xa.XAResource</indexterm></ph>javax.transaction.xa.XAResource</i></li>
<li id="i1018125"><i id="jta75105">javax.transaction.xa.Xid<ph><indexterm>javax.transaction.xa.Xid</indexterm></ph></i></li>
Modified: db/derby/docs/trunk/src/ref/rrefjta94396.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjta94396.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjta94396.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjta94396.dita Fri Mar 30 08:19:13 2007
@@ -33,7 +33,7 @@
the JTA libraries, see <xref format="html" href="http://java.sun.com/products/jta/"
scope="local"><i>http://java.sun.com/products/jta/</i></xref> and download
the specification and javadoc help files for JTA interfaces.</p></li>
-<li><ph conref="refconrefs.dita#prod/productshortname"></ph> (<i>derby.jar</i>)</li>
+<li><ph conref="../conrefs.dita#prod/productshortname"></ph> (<i>derby.jar</i>)</li>
</ul></p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rrefkeywords29722.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefkeywords29722.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefkeywords29722.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefkeywords29722.dita Fri Mar 30 08:19:13 2007
@@ -25,8 +25,8 @@
</keywords>
</metadata></prolog>
<refbody>
-<section><p>This section lists all the <ph conref="refconrefs.dita#prod/productshortname"></ph> reserved
-words, including those in the SQL-92 standard. <ph conref="refconrefs.dita#prod/productshortname"></ph> will
+<section><p>This section lists all the <ph conref="../conrefs.dita#prod/productshortname"></ph> reserved
+words, including those in the SQL-92 standard. <ph conref="../conrefs.dita#prod/productshortname"></ph> will
return an error if you use any of these keywords as an identifier name unless
you surround the identifier name with quotes ("). See <xref href="crefsqlj1003454.dita#crefsqlj1003454"></xref>. <sl
compact="yes">
Modified: db/derby/docs/trunk/src/ref/rreflimits.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreflimits.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rreflimits.dita (original)
+++ db/derby/docs/trunk/src/ref/rreflimits.dita Fri Mar 30 08:19:13 2007
@@ -22,7 +22,7 @@
<title>Derby limitations</title>
<refbody>
<section><p>The section lists the limitations associated with <ph
-conref="refconrefs.dita#prod/productshortname"></ph>.</p></section>
+conref="../conrefs.dita#prod/productshortname"></ph>.</p></section>
</refbody>
</reference>
Modified: db/derby/docs/trunk/src/ref/rreflimitsxml.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rreflimitsxml.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rreflimitsxml.dita (original)
+++ db/derby/docs/trunk/src/ref/rreflimitsxml.dita Fri Mar 30 08:19:13 2007
@@ -26,7 +26,7 @@
</metadata></prolog>
<refbody>
<section><p>The following table lists the limitations on XML data types in <ph
-conref="refconrefs.dita#prod/productshortname"></ph>.</p></section>
+conref="../conrefs.dita#prod/productshortname"></ph>.</p></section>
<table frame="all"><title>XML limitations</title>
<tgroup cols="2" colsep="1" rowsep="1"><colspec colname="colspec0" colwidth="228*"/>
<colspec colname="colspec1" colwidth="228*"/>
Modified: db/derby/docs/trunk/src/ref/rrefnumericlimits.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefnumericlimits.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefnumericlimits.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefnumericlimits.dita Fri Mar 30 08:19:13 2007
@@ -20,7 +20,7 @@
-->
<reference id="rrefnumericlimits" xml:lang="en-us">
<title>Numeric limitations</title>
-<shortdesc>There are limitations on the numeric values in <ph conref="refconrefs.dita#prod/productshortname"></ph>.</shortdesc>
+<shortdesc>There are limitations on the numeric values in <ph conref="../conrefs.dita#prod/productshortname"></ph>.</shortdesc>
<prolog><metadata>
<keywords><indexterm>limitations<indexterm>numeric values</indexterm></indexterm>
<indexterm>data types<indexterm>numeric limitations</indexterm></indexterm>
Modified: db/derby/docs/trunk/src/ref/rrefpgc1.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefpgc1.dita?view=diff&rev=524120&r1=524119&r2=524120
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefpgc1.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefpgc1.dita Fri Mar 30 08:19:13 2007
@@ -24,7 +24,7 @@
<section><p>The JDBC API defines the following parameters for this method
call:</p></section>
<section> <ul>
-<li><i>catalog</i> <p>always use <i>null</i> for this parameter in <ph conref="refconrefs.dita#prod/productshortname"></ph>.</p></li>
+<li><i>catalog</i> <p>always use <i>null</i> for this parameter in <ph conref="../conrefs.dita#prod/productshortname"></ph>.</p></li>
<li><i>schemaPattern</i> <p>Java procedures have a schema.</p></li>
<li><i>procedureNamePattern</i> <p>a String object representing a procedure
name pattern.</p></li>