db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-688) Enhancements to XML functionality to move toward XPath/XQuery support...
Date Sat, 05 Aug 2006 15:17:15 GMT
    [ http://issues.apache.org/jira/browse/DERBY-688?page=comments#action_12425965 ] 
Bryan Pendleton commented on DERBY-688:

Note to reviewers (and to Army): the "phase2" and "phase3" patches appear to have been generated
with full 
absolute file names rather than with relative file names, which means that the simple technique
"cd trunk; patch -p0 < PATCH" fails to locate the files. For review purposes, this is straightforward
to work around: 
once you have downloaded each patch, edit the patch and change the file names to strip out
the leading portion 
of the absoluate file names, so that, for example:

--- c:/p4clients/main_codeline/opensource/java/testing/org/apache/derbyTesting/functionTests/tests/lang/xml_general.sql
Mon Jul 31 11:37:21 2006
+++ c:/private/derby_src/java/testing/org/apache/derbyTesting/functionTests/tests/lang/xml_general.sql
 Mon Jul 31 09:03:47 2006


--- java/testing/org/apache/derbyTesting/functionTests/tests/lang/xml_general.sql Mon Jul
31 11:37:21 2006
+++ java/testing/org/apache/derbyTesting/functionTests/tests/lang/xml_general.sql  Mon Jul
31 09:03:47 2006

In vim, for example, just do:


on each of the phase2 and phase3 patches.

I don't think there's any need to repost all the patches just to fix this, but if we end up
reposting them later,
this would be a nice thing to clean up.

> 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, 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


View raw message