Re: Weird results from WHERE clause ...

This is running in Run SQL Scripts.

Note my earlier comment - the ONLY difference between the working and non-working versions is that we changed the final part of the statement from:

WHERE UniqueId BETWEEN 50 and 50;

to

WHERE UniqueId = 50;

That is the ONLY change I promise.

The first one works correctly - the second doesn’t.

Note also that the non-working version does not fail to return a result - it just doesn’t return any values - they are all blank/null other than the UniqueId itself.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On May 12, 2016, at 11:04 AM, Englander, Douglas <Douglas_Englander@xxxxxxxxxxxxx> wrote:


Jon,

I got the same results as Charles, neither returns empty columns. I tried in iSeries Navigator and STRSQL green screen. Is your SQL running there or in embedded RPG? We are on V7R1.

I would look at the code also. 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!!!

Hope this helps,

Doug

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