Given the earlier description of the file in question John I don't see memory as an issue - besides if it were using XML-INTO with a handler would give "row by row" access and a tiny memory footprint.

Are you sure you mean SAX by the way? Surely processing the DOM is the only way to really be highly selective. XML-INTO can be every bit as selective as XML-SAX since it uses the same path mechanism.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Feb 22, 2019, at 11:12 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

On Fri, Feb 22, 2019 at 6:30 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

If it can be handled by SQL and XML-SAX there's no reason it can't be handled by XML-INTO - and it requires a lot less logic than XM:L-SAX.

There *is* a potential reason, and I already discussed it (actually, I
led with it): SAX (I don't know specifically about XML-SAX, but in
principle, any SAX solution) only needs to operate on a small part of
the document at any given time, and thus requires much less memory for
very large files. If not the whole point of SAX, it's at least one
very important point.

John Y.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].