× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



From: Wilt, Charles

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.

Hmm.  To me, it's actually much easier to debug the RPG, especially on very
complex SQL statements, because I can much more easily review intermediate
steps, whereas with SQL I can only make my analysis based on the final
result (which might in turn require dumping the results to an output file
and then poring through that to determine what went wrong).

I can of course break down the SQL and do it piece by piece, but unlike RPG,
as we've seen it's pretty easy for something in one part of an SQL to break
something in another part, and that's hard to debug when you can't actually
get in the middle of the process.

Joe



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.