Received: from mail1.noris.net (letterman.noris.net [62.128.1.26]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA71619 for ; Tue, 30 May 2000 10:31:50 -0400 (EDT) (envelope-from urlichs@noris.de) Received: from transwarp.backup.noris.net ([10.1.0.131]:15887 "HELO noris.de") by mail.noris.net with SMTP id ; Tue, 30 May 2000 16:31:35 +0200 Received: (qmail 28148 invoked by uid 202); 30 May 2000 16:31:35 +0200 From: "Matthias Urlichs" Date: Tue, 30 May 2000 16:31:35 +0200 To: Jeff MacDonald Cc: omid omoomi , pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Re: 7.0 weirdness Message-ID: <20000530163135.P25517@noris.de> References: <20000530134645.34684.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from jeff@pgsql.com on Tue, May 30, 2000 at 11:10:24AM -0300 X-Archive-Number: 200005/198 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@noris.de | ICQ: 20193661 The quote was selected randomly. Really. | http://smurf.noris.de/ -- Problem mit cookie: File exists