[ http://issues.apache.org/jira/browse/DERBY-334?page=all ]
A B updated DERBY-334:
----------------------
Attachment: derby-xml_v4.stat
derby-xml_v4.patch
Latest patch (_v4) resolves conflicts with recent checkins. This patch also
removes the two new XML tests from the derbyall suite, since we don't want to
require that people running derbyall have Xerces in their classpaths. The two
tests can still be run manually using RunTest. At some point we'll probably
want to create a new XML suite that contains all of the XML tests, but I think
that can be submitted as a seperate patch.
> 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_v4.patch, derby-xml_v4.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
