Re: characters to not use in files with sql and rpgle functions

Doesn't properly escaped SQL bypass these (SQL problem) issues? Use stored
procedures or parameterized queries instead of dynamic SQL. Are you causing
problems downstream by changing the data between the import and export
process?
If you have issues with exporting data to entites that accept (for instance)
US ASCII, this is a presentation problem, not a storage problem. IMO your
filters should be at the point of presentation/export. Store as much of the
original data as possible with as little change as possible.

HTH,
Loyd

On Tue, Aug 17, 2010 at 8:46 AM, <franz400@xxxxxxxxxxxx> wrote:

Need to develop a generic list of characters to strip in imported data from
other systems that could cause problems in various sql processes. We trade
data (import & export) with many systems, in many different formats, and
sometimes issues, or we create issues for others when we pass data on.
Perhaps a better solution is to create a list of characters allowed and
blank all others?
We do a fair amount of re-formatting names & addresses, using %replace,
%scan in rpgle, sql "like" selects, etc.
Generally US data, but names from around the world.
Jim Franz

--
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.