Re: SQL and invalid data in field

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 02/20/2019
04:32:21 PM:

On Wed, Feb 20, 2019 at 4:06 PM <dlclark@xxxxxxxxxxxxxxxx> wrote:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on

02/20/2019

03:55:14 PM:

So occasionally we come across data in our files that SQL does not

like

to play with.
RLA handles it fine. But as we move more towards SQL it is becoming

a

problem.

You say the column is called COLI_CHANGE_DATE. Is the column

data

type actually DATE? You didn't say, but what is the actual data in

the

column when it errors out? The answer to these questions will

determine

the course of action.

sorry dave - no, it is the class 8p0 date field

So, I presume the data is actually low values or blanks (i.e.,
"initialized incorrectly"). I haven't tried this, but it seems you should
be able to supply an indicator array in your SELECT statement and turn on
extended indicator support. Then, if the indicator for that column is a
-2 then you initialize it with zeroes. Still check SQLSTATE, though.


Sincerely,

Dave Clark