|
> 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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.