Re: Tool to check why queries miss results?
- From: "Mark C. Stock" <mcstockX@Xenquery .com>
- Date: Mon, 6 Mar 2006 13:15:08 -0500
"Andreas Koch" <nospam@xxxxxxxxxxxxxxx> wrote in message
news:duhsnj$lku$03$1@xxxxxxxxxxxxxxxxxxxx
: DA Morgan wrote:
: >> The tool doesn't have to "expect" anything - thats what
: >> the user input is for.
: >
: > 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.
:
: Ah ok, so you aren't just flaming, it seems i didn't make
: clear enough what the tool is supposed to do.
:
: Forget the missing constraint. That was just an example
: and i HOPED that would make things easier to understand.
: Seems it only confused people more.
:
: Given :
: An application that is of course much much more complex
: than the example i've given. Lets say 1.000.000 lines
: of SQL functions and views, written by many developers
: over many years.
:
: All tables have perfect constraints and all data
: is perfectly consistant.
:
: One query is expected to return certain values, based
: on its creators understanding of the tables and views
: used in it.
:
: That person may have misunderstood some tables or views,
: or some tables or views may have changed later without
: correctly checking for every possible side effect this
: may have on all statements.
:
: So, the query returns some results but not all results
: THE USER OF THAT STATEMENT WOULD EXPECT.
:
: So, he tells the magic tool:
:
: A) This is the Query i executed
: B) This is what results i got (the tool can get that
: itself of course)
: C) This is a value i would have expected to get, but
: didn't.
:
: I don't look for such a tool because i couldn't debug
: such a problem by hand. I look for such a tool because
: i'd prefer to debug such a problem in 5 seconds instead
: of 5 hours. And if there is no such tool out there,
: i'll probably go and write one myself, sooner or later.
:
:
:
:
:
if you write your test case properly, the 'tool' you need to compare results
consists of the UNION and MINUS operators to returns (set1 minus set2) union
(set2 minus set1)
but it still sounds like you're looking for a tool to tell you why the sets
don't match -- which no tool can do, but a well-designed test plan that
validates the inputs and/or state of data prior to the test will be able to
accomplish
++ mcs
.
- Follow-Ups:
- Re: Tool to check why queries miss results?
- From: Andreas Koch
- Re: Tool to check why queries miss results?
- References:
- Tool to check why queries miss results?
- From: Andreas Koch
- Re: Tool to check why queries miss results?
- From: DA Morgan
- Re: Tool to check why queries miss results?
- From: Andreas Koch
- Re: Tool to check why queries miss results?
- From: DA Morgan
- Re: Tool to check why queries miss results?
- From: Andreas Koch
- Tool to check why queries miss results?
- Prev by Date: Re: Tool to check why queries miss results?
- Next by Date: Re: Tool to check why queries miss results?
- Previous by thread: Re: Tool to check why queries miss results?
- Next by thread: Re: Tool to check why queries miss results?
- Index(es):
Relevant Pages
|
Loading