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

[Mike Jones <mike.jones.sysdev@xxxxxxxxx>]

Hi Vern,

I'd be shocked if XMLTABLE, which uses a SET based approach, doesn't
perform faster.  I can't give you intelligent comparison information,
because XMLTABLE is the ONLY way I've ever parsed XML, and likely the ONLY
way I'll parse it in the future.

Mike

On Wed, Jul 12, 2017 at 11:11 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

> 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