Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <3280093.1153408695416.JavaMail.jira@brutus>
Date: Thu, 20 Jul 2006 08:18:15 -0700 (PDT)
From: "A B (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-688) Enhancements to XML functionality to
 move toward XPath/XQuery support...
In-Reply-To: <1721251321.1131413841258.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-688?page=all ]

A B updated DERBY-688:
----------------------

    Attachment: d688_phase1_v2.patch

Attaching a second patch, d688_phase1_v2.patch, that makes the appropriate changes to ensure that the new classes (esp. SqlXmlExecutor) are included in the jar builds.  For the thread indicating what changes to make, see:

http://article.gmane.org/gmane.comp.apache.db.derby.devel/24135

The patch is the same as phase1_v1 except that it has the following additional diffs:

Index: tools/jar/extraDBMSclasses.properties
===================================================================
--- tools/jar/extraDBMSclasses.properties	(revision 423655)
+++ tools/jar/extraDBMSclasses.properties	(working copy)
@@ -84,4 +84,4 @@
 derby.module.store.urlf=org.apache.derby.impl.io.URLFile
 derby.module.store.cpf=org.apache.derby.impl.io.CPFile
 
-derby.module.xml.typec=org.apache.derby.impl.sql.compile.XMLTypeCompiler
+derby.module.xml.sqlxmle=org.apache.derby.impl.sql.execute.SqlXmlExecutor
Index: tools/jar/extraDBMStypes.properties
===================================================================
--- tools/jar/extraDBMStypes.properties	(revision 423655)
+++ tools/jar/extraDBMStypes.properties	(working copy)
@@ -13,3 +13,4 @@
 derby.module.type.m=org.apache.derby.impl.sql.compile.RefTypeCompiler
 derby.module.type.n=org.apache.derby.impl.sql.compile.TimeTypeCompiler
 derby.module.type.o=org.apache.derby.impl.sql.compile.TimestampTypeCompiler
+derby.module.type.p=org.apache.derby.impl.sql.compile.XMLTypeCompiler

I ran the XML test suite (xmlSuite) with classes and with jars using IBM 1.4.2 and they passed in both cases.

Reviews/feedback are appreciated.

> Enhancements to XML functionality to move toward XPath/XQuery support...
> ------------------------------------------------------------------------
>
>                 Key: DERBY-688
>                 URL: http://issues.apache.org/jira/browse/DERBY-688
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL, JDBC
>            Reporter: A B
>         Assigned To: A B
>            Priority: Minor
>         Attachments: d688_phase1_v1.patch, d688_phase1_v1.stat, d688_phase1_v2.patch, derbyXMLSpec.html
>
>
> As of DERBY-334, Derby has some very basic support for XML that consists of an XML datatype and three operators (XMLPARSE, XMLSERIALIZE, and XMLEXISTS).  I would like to enhance this existing functionality and, by doing so, help to move Derby incrementally toward a more usable and more complete XPath/XQuery solution (with emphasis on "incrementally").
> I have attached to this issue a document describing the particular changes that I am looking to make.  At a high level, they consist of:
> 1) Making it easier to use the XML operators and datatype from within JDBC (ex. by implicit parsing/serialization of XML values).
> 2) Adding a new operator, XMLQUERY, to allow a user to retrieve the results of an XPath expression (instead of just determining whether or not the expression evaluates to an empty sequence, which is what XMLEXISTS does).
> 3) Making changes to the existing operators to line them up with the SQL/XML 2005 specification, and also to take steps toward my eventual hope of having support for XQuery (as opposed to just XPath) in Derby.
> If anyone has time and interest enough to look at the document and provide feedback, that'd be great...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira