Re: A Difference between iACS and RUNSQLSTM on INSERT statement

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Main reason why it's a "best practices" thing to always throw a space after
each comma in a list such as that.
Is this a list, or a decimal?  Myvalue(2,3)  The following clarifies that
Myvalue(2, 3)

On Wed, Sep 6, 2023 at 5:06 PM Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

> I have a table like this:
>      CREATE TABLE custmast (
>          CustID NUMERIC(4, 0) NOT NULL
>          ,Name CHAR(40) NOT NULL
>      ,PRIMARY KEY (Custid)
> )
> This insert statement works in iACS but fails in RUNSQLSTM:
>      INSERT INTO custmast (CustID,Name) VALUES (1,'John Smith');
>
> However, this one works in RUNSQLSTM and iACS:
>      INSERT INTO custmast (CustID,Name) VALUES (1, 'John Smith');
>
> The difference is the extra space after the ",". I had some more
> extensive code that I ran with RUNSQLSTM back in 2022 (I think) on
> PUB400 but it broke today.
>
> Is this a known bug or feature?
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.