On 9/27/16, 1:44 PM, John Yeung wrote:
Now James (or whoever he is speaking for) is trying to introduce
something new, and it's breaking.
Quite correct about the application's own translation table simply
passing control characters through untranslated. Which works just fine,
so long as we're the ones controlling the translation.
The problem is a matter of customer-written code that's doing stuff we'd
never imagined. Customer-written code that worked just fine until they
decided to do it with a prepared statement (and so far as I can
determine, the only thing that usage of a prepared statement even buys
them is protection from SQL injection, and I'm not even convinced that
the situation has enough exposure to where SQL injection is even a
realistic possibility).
At any rate, I've asked to have hex '8E' passed on to the customer.
--
JHHL
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.
midrange.com
