Received: from rage.hub.org (root@nat195.14.mpoweredpc.net [142.177.195.14]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA79604; Wed, 31 May 2000 15:02:21 -0400 (EDT) (envelope-from jeff@pgsql.com) Received: from localhost (bignose@localhost) by rage.hub.org (8.9.3/8.9.3) with ESMTP id QAA76619; Wed, 31 May 2000 16:00:55 -0300 (ADT) (envelope-from jeff@pgsql.com) X-Authentication-Warning: rage.hub.org: bignose owned process doing -bs Date: Wed, 31 May 2000 16:00:55 -0300 (ADT) From: Jeff MacDonald X-Sender: bignose@rage.hub.org Reply-To: Jeff MacDonald To: Matthias Urlichs cc: Jeff MacDonald , omid omoomi , pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Re: 7.0 weirdness In-Reply-To: <20000530163135.P25517@noris.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200005/225 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@noris.de | ICQ: 20193661 > The quote was selected randomly. Really. | http://smurf.noris.de/ > -- > Problem mit cookie: File exists >