Re: Anybody here know anything about doing SQL Prepared Statements from PHP?

Good point on a bad design John <grin>


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Sep 27, 2016, at 4:44 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

On Tue, Sep 27, 2016 at 4:16 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

What confuses me about this whole scenario is why on earth anyone wants an ASCII control character to be retained in an otherwise EBCDIC data stream? When at some point in the future the data gets converted back to ASCII for printing or whatever doesn’t it then get converted back to the wrong value?

James mentioned that "But given that hex'0A' has been entrenched in
the application for over two decades, changing the application is not
an option."

To me, that sounds like "the application" is not relying on "standard"
encoding facilities (such as would be provided by the operating system
or language runtime or what have you), at least not consistently, and
instead has custom raw-byte processing. More than likely, whoever
originally built it did not have the strongest grasp of encoding
issues and simply assumed that a literal x'0A' would Just Work, and in
its original environment, apparently it did.

Now James (or whoever he is speaking for) is trying to introduce
something new, and it's breaking.

John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.