Re: Arrays

<snip>
> SQL is well worth the coin paid to obtain it.  Harness it's power & you'll
> never want to type the command WRKQRY again....
< Thanks,
< Tommy Holden
</snip> 

Haven't typed in WRKQRY in years (~10).  


> I don't find it "that complex".
> Even Joe Pluta occasionally finds SQL useful.  I think that if you never
> use it, then it is like the person who finds he can get everything done
> with a hammer; when it is the only tool in their toolbox.
> 
> Rob Berendt

I don't find SQL too complex by any means.  I find it simple, and have
used it on many platforms.

I guess I see it this way:  You can build your SQL statements, and
build your summaries "on the fly" with no extra code (SQL is code,
BTW), but when you run them, and they take long, what can you do? 
Index.  Study the query optimizer -- what is it choosing?  Why won't
it use my index?  Which type of index?  EVI?  Can I bribe the crazy
thing?  Will it use the index when the user hits the view a little
differently?

I have spent alot of time studying indexing, on DB2 and SQL server as
well.  It is fascinating, but I just find it easier to analyze the
data request I am building, and make my own 'access plan', write the
code to do it, and it's done.  I would bet that any quick-running SQL
statement can be made to run just as fast or even faster using RPG.



-- 
"Enter any 11-digit prime number to continue..."