Re: users pasting hex '41' into char fields... -- MIDRANGE-L

Subject: Re: users pasting hex '41' into char fields...
From: dlclark@xxxxxxxxxxxxxxxx
Date: Wed, 6 Jul 2016 11:21:29 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 07/06/2016
11:15:03 AM:

CHECK (contains(mystring, x'41') <> 1 ))

True, if you just want to avoid that one character value. What we
have found is that we are getting other values in the mix, too. Users
pasting from web pages can get all kinds of ASC-II hex characters into
your EBCDIC data.

By teh way... x'41' is a non-breaking space character (HTML
&nbsp;).

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

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