Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 66998 invoked from network); 25 Aug 2006 03:10:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Aug 2006 03:10:28 -0000 Received: (qmail 24059 invoked by uid 500); 25 Aug 2006 03:10:16 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 24025 invoked by uid 500); 25 Aug 2006 03:10:16 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 23950 invoked by uid 99); 25 Aug 2006 03:10:15 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Aug 2006 20:10:15 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Aug 2006 20:10:14 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8E600410017 for ; Fri, 25 Aug 2006 03:07:05 +0000 (GMT) Message-ID: <3886476.1156475225580.JavaMail.jira@brutus> Date: Thu, 24 Aug 2006 20:07:05 -0700 (PDT) From: "Bryan Pendleton (JIRA)" 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 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-688?page=all ] Bryan Pendleton updated DERBY-688: ---------------------------------- Derby Info: (was: [Patch Available]) Merged the phase7 patch to the 10.2 branch as revision 434583. Cleared Patch Available. Is it time to mark this issue resolved? > 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, d688_phase1_v3.patch, d688_phase2_v1_code.patch, d688_phase2_v1_tests.patch, d688_phase2_v2_tests.patch, d688_phase2_v3_tests.patch, d688_phase3_v1_code.patch, d688_phase3_v1_tests.patch, d688_phase4_v1.patch, d688_phase4_v2.patch, d688_phase5_v1.patch, d688_phase6_v1.patch, d688_phase7_v1.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