RE: SQL under the covers

["Reeve" <news@xxxxxxxxxx>]

And the blisters will turn into festering sores...fortunately, I know
someone else will be looking at my code, and I write it like I'm standing in
front of the Pearly Programming Gates (not Bill, of course) trying to get
into Programmer Heaven.  A CODE that works would be just as good!

-rf

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
> Sent: Monday, July 12, 2004 6:38 PM
> To: 'Midrange Systems Technical Discussion'
> 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.