RE: Suddenly I have SQL Insert errors?

I don't now about always halting... I do know that the likelihood of a city name exceeding 20 characters in our customer database is pretty good.

Now, having said that... I also know that our clients that require these reports (they end up in Excel) are notorious for not even looking at them.
So there is a possibility that the error existed for years and no one noticed.

It was just odd that I found TWO separate issues in the same day with SQL halting.

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of John Yeung
Sent: Wednesday, April 6, 2022 4:25 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Suddenly I have SQL Insert errors?

On Wed, Apr 6, 2022 at 3:58 PM Greg Wilburn
<gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

I hear what you're saying, but I'm not so sure that is the case.
Following that logic, the message would occur any time the value of "city" was longer than 20 (which occurs a lot).
This has been in use for many years.

What are the chances that the severity of the message id changed?

Hm. Well, it's not unheard of for a message to change severity, but I
think that's rare, and I wouldn't have expected this message to have
changed. I mean, the message has been around since forever and,
correct me if I'm wrong, it has never offered to truncate and
continue. So I don't know that severity plays into it.

I am surprised that you would previously have gotten implicit
truncation (and completion of the insert) and now are getting a halt.

Do you know if you are now *always* halting on too-long data? (If only
sometimes, then that would be even more mysterious.)

John Y.