[ http://issues.apache.org/jira/browse/DERBY-334?page=all ]
A B updated DERBY-334:
----------------------
Attachment: derby-xml_v2.stat
derby-xml_v2.patch
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:
http://article.gmane.org/gmane.comp.apache.db.derby.devel/4987
In the meantime, any feedback re: this current (second) version is appreciated.
> Add initial SQL support for XML datatype/functions in Derby, based on
> SQL/XML specs.
> -------------------------------------------------------------------------------------
>
> Key: DERBY-334
> URL: http://issues.apache.org/jira/browse/DERBY-334
> Project: Derby
> Type: New Feature
> Components: SQL
> Versions: 10.1.0.0
> Reporter: A B
> Assignee: A B
> Fix For: 10.1.0.0
> 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:
> http://thread.gmane.org/gmane.comp.apache.db.derby.devel/4468
--
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
