Re: Weird results from WHERE clause ...

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