Re: Returning DISTINCT rows when SQL *DOES NOT* contain distinct!

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Sat, 14 May 2005 16:58:00 -0700
Message-ID: <1116114832.820170@yasure>

vistav20_at_yahoo.com wrote:

> DA Morgan wrote:
>

>>You make me just want to suggest:
>>
>>SELECT UNIQUE id
>>FROM ....;
>>
>>Also doesn't contain the keyword word DISTINCT.
>>
>>Why hasn't anyone asked the OP what the point of the exercise is? I

>
> fail
>

>>to see a premise beyond "my instructor gave me homework."

>
>
> :-)
>
> Hmmm... Not a good idea to write off every query as "my instructor...".
>
> We are trying to optimize the response time from a mission critical
> tool, which bogs down when it gets the result set contains hundereds
> (or thousands) of rows while it should only contain may be 10 or 20!!!
>
> regards,

Not every ... just some.

If what you say is the point of the inquiry then you need to rewrite the SQL statement to be valid with your business logic. There is no alternative.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)

Received on Sat May 14 2005 - 18:58:00 CDT