RE: SQL... MAX AND COUNT?

Personally, I think a lot of it is that we're used to detailed specs for
RPG whereas SQL is "magic" and a simple spec should suffice.

You and I both know SQL isn't magic.

And yes, I'd agree that it's easy to create a SQL statement that looks
right but isn't.  On the other hand, IMHO when an SQL statement is
wrong, it's usually obvious from the results; and the way the results
wrong are usually help clue you in on why the statement is wrong.  On
the other hand, an error in RPG logic is usually harder to track down
since you are dealing on a per-record basis instead of an entire set.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx 
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Wednesday, January 03, 2007 2:34 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: SQL... MAX AND COUNT?

From: Wilt, Charles

Now, Joe...lets not blame SQL for the confusion caused by the OP's
description of his requirements not being exact.

<smirk>

You're right, of course.  But still, maybe it's just me but 
it would be a
lot easier for me to see in an RPG program what was going on. 
 It just seems
easy to create an SQL statement that LOOKS correct but has some inner
relationship that's not easy to see.

Then again, if you commented the heck out of the statement, it would
probably help.

Joe


-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) 
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.