Re: [HACKERS] Re: 7.0 weirdness

From: Jeff MacDonald <jeff(at)pgsql(dot)com>
To: Matthias Urlichs <smurf(at)noris(dot)de>
Cc: Jeff MacDonald <jeff(at)pgsql(dot)com>, omid omoomi <oomoomi(at)hotmail(dot)com>, pgsql-sql(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Re: 7.0 weirdness
Date: 2000-05-31 19:00:55
Message-ID: Pine.BSF.4.21.0005311600220.2897-100000@rage.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

thanks for the hlep guys..

for those that are curious, the distinct is tehr cause it's
someone elses code that i'm workig on .. :) have to kick
out the bug's//

jeff

On Tue, 30 May 2000, Matthias Urlichs wrote:

> Hi,
>
> Jeff MacDonald:
> > gid is unique.. it's a serial..
> >
> Then there is no point in using "DISTINCT" in the first place, is there?
>
> > funny thing is tho this worked on 6.5
>
> It happened to work because your gid is unique. But in the general case,
> it can't work. Consider this table:
>
> gid created
> X 1
> Y 2
> X 3
>
> Now, should your query's result be
>
> gid
> X
> Y
>
> or should it be
>
> gid
> Y
> X
>
> ? And since the typical implementation throws away non-selected-for
> columns before UNIQUEing, how should it be able to sort anything?
>
> --
> Matthias Urlichs | noris network GmbH | smurf(at)noris(dot)de | ICQ: 20193661
> The quote was selected randomly. Really. | http://smurf.noris.de/
> --
> Problem mit cookie: File exists
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-05-31 19:34:44 Re: config files in /data
Previous Message Peter Eisentraut 2000-05-31 18:44:03 Re: SET FSYNC command?

Browse pgsql-sql by date

  From Date Subject
Next Message Jon Parise 2000-05-31 19:05:15 Inheritance heirarchy
Previous Message Brian Powell 2000-05-31 18:55:09 creating rules on joined views