db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: [jira] Updated: (DERBY-334) Add initial SQL support for XML datatype/functions in Derby, based on SQL/XML specs.
Date Wed, 08 Jun 2005 22:16:32 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
I couldn't apply the latest XML patch... Lots of changes have happened
in SQLgrammar.jj file since this was submitted. Also some differences
in two other files. Can you please submit an updated patch? I will work
on getting that committed soon.<br>
A B (JIRA) wrote:<br>
  <pre wrap="">     [ <a class="moz-txt-link-freetext" href="http://issues.apache.org/jira/browse/DERBY-334?page=all">http://issues.apache.org/jira/browse/DERBY-334?page=all</a>

A B updated DERBY-334:

    Attachment: derby-xml_v2.stat

Attaching second version of the patch to address the issues brought up by Satheesh.  In particular:

1 - Simplified logic to check for XML values in a top-level SELECT/VALUES statement.  New
logic is similar to the existing logic for rejecting parameter markers in the same situation.

2 - Consolidated the XMLParseOperatorNode and XMLSerializeOperatorNode classes into UnaryOperatorNode;
also consolidated the XMLExistsOperatorNode class into BinaryOperatorNode.

3 - Added example of how to query using namespaces to the XML impl class, and added test cases
to the lang/xml_general.sql test.

4 - Removed the assumption that  the only valid type of an XML "constant" is a null value.
 Satheesh said that this assumption was false, though I couldn't come up with an example to
test it.  If anyone knows of such an example, please post...

5 - Fixed XML binding so that the correct behavior occurs in both embedded and Network Server
modes.  In the first version of the patch, attempts to bind to an XML column over the server
weren't properly caught and the result was a protocol exception with connection deallocation.
 This version of the patch fixes that problem.

I am now going to begin a third version of the patch to address Dan Debrunner's comments as
found here:

<a class="moz-txt-link-freetext" href="http://article.gmane.org/gmane.comp.apache.db.derby.devel/4987">http://article.gmane.org/gmane.comp.apache.db.derby.devel/4987</a>

In the meantime, any feedback re: this current (second) version is appreciated.

  <blockquote type="cite">
    <pre wrap="">Add initial SQL support for XML datatype/functions in Derby,  based
on SQL/XML specs.

         Key: DERBY-334
         URL: <a class="moz-txt-link-freetext" href="http://issues.apache.org/jira/browse/DERBY-334">http://issues.apache.org/jira/browse/DERBY-334</a>
     Project: Derby
        Type: New Feature
  Components: SQL
    Reporter: A B
    Assignee: A B
     Fix For:
 Attachments: derby-xml_v2.patch, derby-xml_v2.stat

Adding some "starter" XML functionality to Derby, which can then serve as the basis for future
XML development.  Initial features include the following:
1 - A built-in XML datatype.
2 - An XMLPARSE() operator for creating XML values.
3 - An XMLSERIALIZE() operator for serializing XML values to strings (for data retrieval).
4 - An XMLEXISTSTS() operator for running simple existence queries against XML using XPath.
These features are implemented at the SQL level only (no JDBC support).  See the email here
for a more detailed description:
<a class="moz-txt-link-freetext" href="http://thread.gmane.org/gmane.comp.apache.db.derby.devel/4468">http://thread.gmane.org/gmane.comp.apache.db.derby.devel/4468</a>
  <pre wrap=""><!---->

View raw message