Return-Path:
Delivered-To: apmail-db-derby-commits-archive@www.apache.org
Received: (qmail 97046 invoked from network); 22 Aug 2006 17:40:41 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur.apache.org with SMTP; 22 Aug 2006 17:40:41 -0000
Received: (qmail 44350 invoked by uid 500); 22 Aug 2006 17:40:40 -0000
Delivered-To: apmail-db-derby-commits-archive@db.apache.org
Received: (qmail 44332 invoked by uid 500); 22 Aug 2006 17:40:40 -0000
Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help:
list-unsubscribe:
List-Post:
Reply-To: "Derby Development"
List-Id:
Delivered-To: mailing list derby-commits@db.apache.org
Received: (qmail 44321 invoked by uid 99); 22 Aug 2006 17:40:40 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 10:40:40 -0700
X-ASF-Spam-Status: No, hits=-9.4 required=10.0
tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [140.211.166.113] (HELO eris.apache.org) (140.211.166.113)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 10:40:39 -0700
Received: by eris.apache.org (Postfix, from userid 65534)
id 52C181A981A; Tue, 22 Aug 2006 10:40:19 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r433708 - in /db/derby/docs/trunk/src/devguide:
cdevdvlp30653.dita cdevstandards805975.dita cdevstandardsxml.dita
derbydev.ditamap
Date: Tue, 22 Aug 2006 17:40:18 -0000
To: derby-commits@db.apache.org
From: jta@apache.org
X-Mailer: svnmailer-1.0.8
Message-Id: <20060822174019.52C181A981A@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
Author: jta
Date: Tue Aug 22 10:40:17 2006
New Revision: 433708
URL: http://svn.apache.org/viewvc?rev=433708&view=rev
Log:
DERBY-1655 (partial): Add documentation for XML functionality to the Developers
Guide.
Committed patch derby1655_devguide2.diff by Laura Stewart .
Added:
db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita (with props)
Modified:
db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita
db/derby/docs/trunk/src/devguide/cdevstandards805975.dita
db/derby/docs/trunk/src/devguide/derbydev.ditamap
Modified: db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita?rev=433708&r1=433707&r2=433708&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevdvlp30653.dita Tue Aug 22 10:40:17 2006
@@ -1,5 +1,5 @@
-
+
-Database limitations
+ database limitations
databases
have a few limitations.
-Limitationsin current version
-Indexeslimitations ofnot supported
-for CLOB, BLOB, and LONG VARCHAR data types
+limitationsDerby databases
+indexeslimitations
-
-- Indexes are not supported for columns defined on CLOB, BLOB, and LONG
-VARCHAR data types.
If the length of the key columns in an index
-is larger than half the page size of the index, creating an index on those
-key columns for the table fails. For existing indexes, an insert of new rows
-for which the key columns are larger than half of the index page size causes
-the insert to fail.
It is generally not recommended to create indexes
-on long columns. It is best to create indexes on small columns that provide
-a quick look-up to larger, unwieldy data in the row. You might not see performance
-improvements if you index long columns. For information about indexes, see .
-- The system shuts down if the database log cannot allocate more disk
-space.
A "LogFull" error or some sort of IOException will
-occur in the derby.log if the system runs out of space. If the system
-has no more disk space to append to the derby.log, you might not see
-the error messages.
-
+IndexesIndexes are not supported for columns defined
+on CLOB, BLOB, LONG VARCHAR, and XML data types.
If the length of the
+key columns in an index is larger than half the page size of the index, creating
+an index on those key columns for the table fails. For existing indexes, an
+insert of new rows for which the key columns are larger than half of the index
+page size causes the insert to fail.
Avoid creating indexes on long
+columns. Create indexes on small columns that provide a quick look-up to larger,
+unwieldy data in the row. You might not see performance improvements if you
+index long columns. For information about indexes, see .
+System shutdownsThe system shuts down if the database
+log cannot allocate more disk space.
A "LogFull" error or some sort
+of IOException occurs in the derby.log file
+when the system runs out of space. If the system has no more disk space to
+append to the derby.log file, you might not see the error
+messages.
Modified: db/derby/docs/trunk/src/devguide/cdevstandards805975.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstandards805975.dita?rev=433708&r1=433707&r2=433708&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstandards805975.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevstandards805975.dita Tue Aug 22 10:40:17 2006
@@ -1,5 +1,5 @@
-
+
-CLOB, and BLOB
+CLOB and BLOB
supports
the standard CLOB and BLOB data types. BLOB and CLOB values are limited to
a maximum of 2,147,483,647 characters.
-
+
+data typesCLOBdata
+typesBLOB
+
Added: db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita?rev=433708&view=auto
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita (added)
+++ db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita Tue Aug 22 10:40:17 2006
@@ -0,0 +1,68 @@
+
+
+
+
+
+XML data types and operators
+ supports
+the XML data type and a set of operators that work with the XML data type.
+The XML data type and operators are based on a small subset of the SQL/XML
+specification.
+
+SQL standardsXML data types and operators
+XML data typesSQL standardXML
+data typeslimitations
+
+
+The XML data type and operators are defined only in the SQL layer.
+There is no JDBC-side support for XML data types. It is not possible to
+bind directly into an XML value or to retrieve an XML value directly from
+a result set. Instead, you must bind and retrieve the XML data as Java strings
+or character streams by explicitly specifying the appropriate XML operator
+as part of the SQL statements:
+- Use the XMLPARSE operator for binding data into XML values.
+- Use the XMLSERIALIZE operator to retrieve XML values from a result set.
+
Additionally, there is no JDBC metadata support for the XML data type.
+The XML data type is not allowed in any of the clauses or operations that
+are described in the section on expressions
+on LONG data types.
+For the XML operators to work properly, requires
+that a JAXP parser, such as Apache Xerces, and Apache Xalan are included in
+the Java classpath. If either the parser or Xalan are missing from the classpath, disallows any XML-related
+operations.
+To see a list of the versions of the JAXP implementation and of Apache
+Xalan that have been tested with XML
+support, see to the release
+notes. The release notes are available from the Apache Derby Downloads page.
+Most Java virtual machines (JVMs) that are version 1.4 or later have
+a JAXP parser embedded in the JVM. If you are using one of these JVMs, you
+do not need to add any other JAXP classes to your classpath. Additionally,
+if the JVM that you are using includes an embedded version of Xalan, you should
+confirm that the version of Xalan satisfies the minimum requirements for . For example, if your
+JVM is Sun JDK 1.4.2, you must override the version of Xalan in the JVM with
+a newer version. Use Java's Endorsed Standards Override Mechanisms described
+at http://java.sun.com/j2se/1.4.2/docs/guide/standards/ to
+override the version of Xalan. If the JVM that you are using does not have
+a JAXP parser or a version of Xalan, you can add external versions of those
+classes in your classpath and will
+pick up those classes.
+
+
Propchange: db/derby/docs/trunk/src/devguide/cdevstandardsxml.dita
------------------------------------------------------------------------------
svn:eol-style = native
Modified: db/derby/docs/trunk/src/devguide/derbydev.ditamap
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/derbydev.ditamap?rev=433708&r1=433707&r2=433708&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/derbydev.ditamap (original)
+++ db/derby/docs/trunk/src/devguide/derbydev.ditamap Tue Aug 22 10:40:17 2006
@@ -1817,7 +1817,7 @@
-
+
@@ -1840,7 +1840,7 @@
-
+
@@ -1862,7 +1862,7 @@
-
+
@@ -1883,7 +1883,7 @@
-
+
@@ -1903,7 +1903,7 @@
-
+
@@ -1921,7 +1921,7 @@
-
+
@@ -1937,7 +1937,7 @@
-
+
@@ -1963,7 +1963,7 @@
-
+
@@ -1971,7 +1971,7 @@
-
+
@@ -1997,6 +1997,13 @@
+
+
+
+
+
+
+
@@ -2435,24 +2442,26 @@
-
+
+
+
+
+
+
+
+
+
+
+
-
-
-
-
-
-
-
-
+
-