RE: Good stuff on SQL techniques

[rob@xxxxxxxxx]

I really have a problem with some of these general statements from so 
called experts.  Like anything using a cursor is not a good use for SQL. 
Oftentimes you couldn't do it with a procedural program (without the use 
of OPNQRYF).  There are numerous other statements made that make you 
cringe when stated by people that you otherwise have great respect for.  I 
could give examples, but that would start the thread off on a tangent.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/21/2003 12:52 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: Good stuff on SQL techniques


> From: Vern Hamberg
>
> Here is a webcast on SQL techniques. I think it's very helpful -
> speaker was (is?) on ANSI standards committee for SQL. I believe
> it can open your mind to new ways of doing things.

I also find it interesting that he specifically states that SQL should not
be used for row-at-a-time processing, or for complex calculations.  In
effect, he's saying that SQL should be used to replace procedural code.

Whiule there ARE things that benefit from set-based approaches, that does
not include all programming tasks.  And in particular, he suggests that
anything using a cursor is not a good use of SQL.  That's almost heretical
with the SQL-for-everything crowd.

Joe

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