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

The thing that bothers me is the difference between "sanitizing data for
internal use" versus "sanitizing data and distributing to others".

For a silly example, let's suppose we collect addresses and don't like
"Lane". So on the import, "Lane" is stripped from the street address.
Suppose there's a city with Main Street, Main Drive, and Main Lane. If there
is a 100 Main Street and 100 Main Lane, where is "100 Main" delivered?

This is why I advocated retaining as much of the imported data as possible
without change, and only transforming it on the presentation (output)
operation.

--Loyd




On Tue, Aug 17, 2010 at 12:09 PM, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx

wrote:

Hi Jim,

Are you building the SQL statements dynamically with concatenation? If
so, why?

Normally, in RPG, you'd use embedded SQL and build your statement as a
static statement. In this case, having a single quote in your "select
where like" wouldn't do any harm!

But (although you haven't said this) I'm assuming you're building the
statement dynamically... because I can't come up with any other reason
why you'd have a problem like that. If that's the case, you can simply
use parameter markers to solve the "special characters" problem. But I
don't know why you'd do that instead of a static statement.

Can you please clarify your situation?