Received: from rage.hub.org (root@nat196.87.mpoweredpc.net [142.177.196.87]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA78663 for ; Tue, 30 May 2000 09:46:50 -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 KAA69991; Tue, 30 May 2000 10:46:45 -0300 (ADT) (envelope-from jeff@pgsql.com) X-Authentication-Warning: rage.hub.org: bignose owned process doing -bs Date: Tue, 30 May 2000 10:46:30 -0300 (ADT) From: Jeff MacDonald X-Sender: bignose@rage.hub.org Reply-To: Jeff MacDonald To: Patrick FICHE cc: Jeff MacDonald , Pgsql-Sql Subject: RE: 7.0 weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.org id JAC78834 X-Archive-Number: 200005/195 gid is unique.. jeff On Tue, 30 May 2000, Patrick FICHE wrote: > It seems to me that it was lack of control in 6.5 version... > For one "gid", you may have several "created" values, so Postgres is not > able to decide which value must be taken and ordered > > Simple example > gid created > 1 1 > 1 3 > 2 2 > > In which order is Postgres supposed to give the data??? > > > Patrick Fiche > -----Message d'origine----- > De : pgsql-sql-owner@hub.org [mailto:pgsql-sql-owner@hub.org]De la part > de Jeff MacDonald > Envoyé : mardi 30 mai 2000 14:28 > À : pgsql-sql@postgresql.org; pgsql-hackers@postgresql.org > Objet : [SQL] 7.0 weirdness > > > hi folks, > > this query works fine in 6.5 but screwie in 7.0 > > 7.0 > > gm=> SELECT DISTINCT gid FROM members > gm-> WHERE active = 't' > gm-> AND (gender = 0 > gm-> AND (wantrstypemale LIKE '%Short Term%' > gm-> OR wantrstypemale like '%Marriage%' > gm-> OR wantrstypemale like '%Long Term%' > gm-> OR wantrstypemale like '%Penpal%' > gm-> OR wantrstypemale like '%Activity Partner%') > gm-> ) order by created desc; > ERROR: For SELECT DISTINCT, ORDER BY expressions must appear in target list > gm=> > > > any idea's ? > > jeff > > > >