Re: Weird results from WHERE clause ...

Chuck,

I've been bitten by this type of thing before as well so I'll take this
opportunity, if you don't mind, to ask - if the first example is valid,
what does it do?:
select col01 col02, col03
from file01 file02


Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144


On 12 May 2016 at 12:01, CRPence <crpbottle@xxxxxxxxx> wrote:

On 12-May-2016 10:04 -0500, Englander, Douglas wrote:

<<SNIP>> I had a missing comma the other day, the SQL Precompiler
accepted it, the RPG compiler accepted it, and the program ran. But
the results were not what I was looking for. I combed through the
joblog and found the SQL error. Once I added the comma, everything
was as expected. Why the precompiler doesn't recognize a missing
comma as an error is beyond me; IT SHOULD!!!

If /should/, then that implies a defect; defects should be reported to a
service provider. However, consider:

A comma that is /missing/, according to the perspective of the
programmer, is not necessarily also /missing/ according to the validity of
a statement, from the perspective of the parser of the language.

The following two statements, for example, are both valid, and quite
different [likely even, incompatible for most usages], despite someone
might argue that the first statement is /missing/ a comma in either or both
of the two clauses:

select col01 col02, col03
from file01 file02

select col01, col02, col03
from file01, file02

--
Regards, Chuck

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.