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


  1.  Home
  2. RPG400-L
  3. March 2022

Re: SQL0117 - Statement contains wrong number of values

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.

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.