A B (JIRA) wrote: > [ 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. >>-------------------------------------------------------------------------------------
+1 on getting this initial XML support into Derby. Even though the patch has already in, I will try to review the new version sometime. At some point the testing does need to be part of the regular derby suite though I think the current approach is good. I need to understand the dependency on xerces, and if the default XML parser supplied by the VM can be used instead. This is probably a good example of open source, get some initial working functionality (incremental development) and then see if it can be improved by others. Dan.
