Re: SQL and invalid data in field -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

"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

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

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

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.