|
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.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 theI'm not vested in XML-SAX or XMLTABLE, but Vern has sent some mixed
XMLTABLE path now; I see no reason to try to pull him off it at this
point.
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.
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.
In regard to "a problematic rewrite", Vern indicated that 13 tables would
be updated from the XML file, which seems somewhat relevant.
As an Amazon Associate we earn from qualifying purchases.
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.