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

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Mike

Thanks, this is encouraging - and others related to the project like 
what I showed in one example.

So one question has been, will it perform in less time - I suspect it 
well - overall there are around 13 tables that will be populated using 
data from the XML. Currently, when there is a parsing error, that goes 
to someone to fix manually.

The SQL stuff has automagically put an x'3F' where the "evil woes" 
reside. Nice - no manual effort needed at all.

As I said to one of the other developers, "Do I have to work hard to 
convince you that no errors is a good thing?" He laughed heartily!

Cheers
Vern

On 7/12/2017 12:01 PM, Mike Jones wrote:
> 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