[ http://issues.apache.org/jira/browse/DERBY-688?page=comments#action_12430271 ] A B commented on DERBY-688: ---------------------------
I've created two new Jira issue, DERBY-1758 and DERBY-1759, for the remaining XML work described in the comments for this issue. I think that those remaining tasks could require a non-trivial effort and thus they merit they own Jira issues. Thus, if/when the phase 7 patch is reviewed/committed, I think we can close this issue (finally) and then work on the other issues separately. Note that the new issues (esp. the testing one, DERBY-1758) may not make it into the 10.2 release, but should still be addressed sooner rather than later. If DERBY-1759 does not make it, then at the very least a release note will be needed to call out the fact that Derby 10.2 doesn't follow SQL/XML serialization rules in some cases. > 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: JDBC, SQL > 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
