RE: SQL under the covers

[rob@xxxxxxxxx]

I hear you Joe.  I once had to modify a matching record sort program and 
buggered that up good.  I'll take debugging SQL anyday over that.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/12/2004 05:37 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: SQL under the covers






> From: Reeve
> 
> In simple terms, I'm
> wondering how I debug a complex SQL statement that doesn't work, and I
> guess there's no easy way to do it.

This is the one blistering flaw in the whole SQL concept.  When it
doesn't work, you can't set breakpoints to find out why.  With native
I/O, I can always walk through the code line by line to figure out
what's going on, but with SQL, once you get past a certain level of
complexity, it's really trial and error until you get it right (and God
help the person who has to modify your code).

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.