Wow, great work Army, and thanks for the careful review and effort by
Brian and Yip! It's great to have this in. If I could only grok
exactly what the feature is and how I might use it :) I am telling
people "we have XML features" and I know it's something to do with
XQuery and XPath, but I couldn't say what.
Did these patches include documentation? Or is that forthcoming?
David
Bryan Pendleton (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-688?page=all ]
Bryan Pendleton updated DERBY-688:
----------------------------------
Derby Info: (was: [Patch Available])
Committed d688_phase3_v1_code.patch and d688_phase3_v1_tests.patch
to subversion as revision 429847. Committed the two patches together per
Army's recommendation to commit these patches as a unit to avoid test diffs.
Clearing the patch available flag because all the pending patches have now been
committed.
Thanks for all the hard work on this, Army!
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...
