× 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.



Over the years, I developed the habit of a blank before AND after items in a parm list or IN list of values.
Did the same for SQL (comma separators) and RPG (colon separators).

Not for international issues, but for clarity.

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power




-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Thursday, September 7, 2023 4:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: A Difference between iACS and RUNSQLSTM on INSERT statement

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.


--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.