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 Thu, 10 Aug 2006 02:53:15 GMT
    [ http://issues.apache.org/jira/browse/DERBY-688?page=comments#action_12427085 ] 
            
Bryan Pendleton commented on DERBY-688:
---------------------------------------

I looked at the Phase 4 patch. It applies and builds cleanly for me. 
However, when I run lang/xml_general.sql, I get the following diff,
which appears to come from the tests of SYSCS_EXPORT_QUERY.

-bash-2.05b$ java org.apache.derbyTesting.functionTests.harness.RunTest lang/xml_general.sql
*** Start: xml_general jdk1.4.2_11 2006-08-09 19:51:14 ***
137 del
< 0 rows inserted/updated/deleted
137a137,138
> ERROR XJ001: Java exception: 'java.security.AccessControlException: access denied (java.io.FilePermission
xmlexport.del write)'.
> ERROR XJ001: Java exception: 'access denied (java.io.FilePermission xmlexport.del write):
java.security.AccessControlException'.
141 del
< 0 rows inserted/updated/deleted
141a142,143
> ERROR XJ001: Java exception: 'java.security.AccessControlException: access denied (java.io.FilePermission
xmlexport.del write)'.
> ERROR XJ001: Java exception: 'access denied (java.io.FilePermission xmlexport.del write):
java.security.AccessControlException'.
Test Failed.
*** End:   xml_general jdk1.4.2_11 2006-08-09 19:51:22 ***


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

        

Mime
View raw message