Re: SQL0117 - Statement contains wrong number of values -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: SQL0117 - Statement contains wrong number of values
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Thu, 3 Mar 2022 11:14:50 -0500
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

On Thu, Mar 3, 2022 at 10:01 AM Stephen Landess
<steve_landess@xxxxxxxxxxx> wrote:

Correction:

In short, the best practice is to always put a space after a comma in an embedded SQL statement if there is ever a possibility that the code
will be COMPILED on a system which uses the comma as the decimal separator.

Honestly, I think the best practice is to always put a space after ANY
comma in ANY programming language, so long as that comma is not meant
to be part of a number.

We do not need to scrimp and save on disk space for our source code.
We can afford to include whitespace for, y'know, readability.

John Y.

This mailing list archive is Copyright 1997-2026 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.