db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-688) Enhancements to XML functionality to move toward XPath/XQuery support...
Date Wed, 26 Jul 2006 00:07:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-688?page=all ]

A B updated DERBY-688:
----------------------

    Attachment: d688_phase2_v1_code.patch
                d688_phase2_v1_tests.patch

Attaching a "phase 2" patch that does the following:

- Adds syntax and binding logic for XMLQUERY operator

- Updates syntax for XMLEXISTS to match XMLQUERY and does some refactoring so that the two
can share code.  The most user-visible change in this area is the change from BY VALUE to
BY REF syntax, which required test updates and corresponding master file updates.

Also as part of these changes I've rewritten some of the parse logic to make it more easily
extendible to a broader XMLQUERY syntax (as defined in SQL/XML[2006]) when/if Derby supports
the broader syntax (esp. optional context items and variable bindings) in the future.

- These phase 2 patches do *not* actually implement the XMLQUERY operator yet; they just allow
parsing and binding of the operator.  Execution-time logic will come in a subsequent patch.

For the sake of review I've separated the Phase 2 patches into two different parts:

  d688_phase2_v1_code.patch: The code changes.
  d688_phase2_v1_tests.patch: The test/master changes.

When committed, though, *both* patches should be committed together in order to avoid test
diffs.

NOTE: The phase 2 changes rely on the Phase 1 changes, which have not yet been committed.
 The phase 2 diffs are created w.r.t the phase 1 diffs and thus the phase 2 patches will not
apply unless the phase 1 patch has been applied first.

I'm still looking for someone to review/commit the phase 1patch (d688_phase1_v3.patch).

I ran derbyall on Windows 2000 with ibm142 after applying the phase 1 patch AND both phase
2 patches; there were no new failures.  I also ran xmlSuite and all XML-specific tests passed.

If anyone has time to review the phase 1 and/or phase 2 patches, I'd be grateful.

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

        

Mime
View raw message