× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Response inline

On 7/13/2017 5:58 PM, Nathan Andelin wrote:
That was the basic idea of my suggestion, though I would recommend
against 819 (no need to be that restrictive).

Okay, there are a lot of CCSID alternatives to pick from.


I actually thought this
was merely a minor variation on your original filtering suggestion.
But it would seem XMLTABLE happens to provide both filtering and
parsing, which is an unbeatably attractive proposition for Vern (and
I'm sure for many folks).


Running the CPY command just prior to the XML-SAX opcode is quite trivial.



He seems to be happily going down the
XMLTABLE path now; I see no reason to try to pull him off it at this
point.

I'm not vested in XML-SAX or XMLTABLE, but Vern has sent some mixed
signals. First that XMLTABLE would mean a problematic rewrite, then later
he "saw the light", which I took to mean that he viewed XMLTABLE as the
better option.
I don't think this is mixed signals - it reflects a sequence of events, I think, when first looking at solutions to the emoji issue.
1. We (not just I) decided we should continue to use the current XML-SAX process and get it to give us better results - this was due to the sense of risk of using something completely new, no matter how much I thought it would work
2. When the XML-SAX process was changed and looked good, testing raised other issues.
3. I did a little POC on getting the data from the XML with using XMLTABLE - I'd seen it at COMMON and thought it would do all we wanted
4. My boss said to go ahead

In regard to "a problematic rewrite", Vern indicated that 13 tables would
be updated from the XML file, which seems somewhat relevant.
This has not resulted in problems yet - I've converted about 5 of the tables to data coming through XMLTABLE, and the very single-case test has not shown any performance decline. And the code is much more direct, hence easier to maintain.

The problem part was the matter of risk of using a new unproven (to us) technology in a situation with pretty high urgency.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.