Re: Tool to check why queries miss results?
Date: Mon, 06 Mar 2006 08:59:10 -0800
Message-ID: <1141664338.94012_at_jetspin.drizzle.com>
Andreas Koch wrote:
> DA Morgan wrote:
>
>
[Quoted] >> And why would any person expect London much less a tool.
>
> A person would expect London because the query is intended
> to show all customers, and their cities and businesses.
How would the tool know that?
> "We have a customer in London, why isn't he on the list!"
Because your SQL statement is poorly written. How is the tool supposed to know you didn't intend the result you got?
> The tool doesn't have to "expect" anything - thats what
> the user input is for.
[Quoted] So the user would go to the tool and input all of the things that are supposed to result from the query before the query is run? Sounds like you'd need a query to know that.
>> If someone doesn't have the requisite skills to write a >> SQL statement they should just learn how to say "Do you >> want fries with that?"
>
> Yea, banish all debuggers for real cool guys don't ever
> make errors.
I don't try to tune my Jaguar. I go to someone that has that expertise and talent. I don't make sails for my boat either. I go to someone with the expertise and talent. If you can't write a good SQL statement then perhaps the problem does not reside with the tool du jour.
-- Daniel A. Morgan http://www.psoug.org damorgan_at_x.washington.edu (replace x with u to respond)Received on Mon Mar 06 2006 - 17:59:10 CET