Re: XML-SAX *XML_EXCEPTION event and reported parsed length question

Hi Richard

Not an option for us - and SQL on IBM i now has really good XML processing. Uses XPath and XQuery and all to get the stuff you want.

I've just been given the go-ahead to see what I can get done with it - the XMLPARSE table function takes the UTF-8 from the XML file and puts up an x'3F' when it can't convert to EBCDIC - very nice and very fast. And missing elements are returned as nulls - they can be forced toa default - and multiple sections result in multiple rows of the result set

Vern

On 7/12/2017 1:57 PM, Richard Schoen wrote:

Vern,

Not sure if this is in your consideration, but VB.Net and C# make XML handling quite trivial and you can interface easily to IBMi.

Regards,


Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
----------------------------------------------------------------------

message: 1
date: Wed, 12 Jul 2017 10:01:36 -0700
from: Mike Jones <mike.jones.sysdev@xxxxxxxxx>
subject: Re: XML-SAX *XML_EXCEPTION event and reported parsed length
question

Hi Vernon,

Three cheers for just considering using the SQL XML functionality (XMLTABLE function), even if you don't end up using it.

I helped someone parse some XML on one of these forums once and had it working using XMLTABLE in about an hour. Days later, the person was still tinkering around trying to get the more laborious ways of parsing to work.

Best wishes for a speedy solution...

Mike

On Tue, Jul 11, 2017 at 2:50 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

I'm aware of - and would like to use - the SQL XML functionality,
which does NOT seem to have these problems - I've tried a few bits.
Problem is, it'd be a rewrite of this program.

Cheers
Vern