[ http://issues.apache.org/jira/browse/DERBY-688?page=comments#action_12430532 ] A B commented on DERBY-688: ---------------------------
> Merged the phase7 patch to the 10.2 branch as revision 434583. Thank you, Bryan, for continuing to review and commit the patches for this issue the whole way through. I appreciate your time and thoroughness! > Cleared Patch Available. Is it time to mark this issue resolved? I think that the work commited for this issue puts Derby XML support into an acceptable state for exposing "first step" XML support that is in line with the relevant standards (namely, SQL/XML 2006). The remaining work has been separated out into two new Jira issues that can be addressed independently, one of which (DERBY-1759) is important for standards compliance and thus is next on my list for 10.2 (hopefully). While those two remaining tasks do need to be completed, I think that Derby XML support as of the "phase 7" commit is in a form that is "complete enough" for the 10.2 release (with the potential need for a release note if DERBY-1759 isn't resolved by then). Thus I believe this issue can be resolved and closed. If I don't hear any objections by the end of today (PST on 08/25), that's what I'll do. Any other bugs/tasks that come up can then be filed as separate Jira issues. Thanks again to Bryan for his continued reviews/commits, Yip for his review of the initial patches, and to David Van Couvering for an initial review of the doc patches (see DERBY-1655). > 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
