Received: from styx.apartia.int (postfix@r34m39.cybercable.tm.fr [195.132.34.39]) by hub.org (8.10.1/8.10.1) with ESMTP id e8KIQSs60529 for ; Wed, 20 Sep 2000 14:26:28 -0400 (EDT) Received: by styx.apartia.int (Postfix, from userid 1000) id 3CCC05A7B; Wed, 20 Sep 2000 20:25:56 +0200 (CEST) Date: Wed, 20 Sep 2000 20:25:56 +0200 From: Louis-David Mitterrand To: sqllist Subject: Re: [Fwd: Re: no ORDER BY in subselects?] Message-ID: <20000920202556.A1388@styx> Reply-To: ldm@apartia.ch Mail-Followup-To: sqllist References: <39C8E3C9.D1CFFDB3@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39C8E3C9.D1CFFDB3@agliodbs.com>; from josh@agliodbs.com on Wed, Sep 20, 2000 at 09:20:25AM -0700 X-Archive-Number: 200009/157 On Wed, Sep 20, 2000 at 09:20:25AM -0700, Josh Berkus wrote: > > At 15:23 20/09/00 +0200, Louis-David Mitterrand wrote: > > > > > >ERROR: parser: parse error at or near "order" > > > > > >Aren't ORDER BY clauses allowed in subselects? > > > > > > > It is a very very sad fact, but, no, they're not. > > Hmmmm ... can't say as I've ever seen an ORDER BY in a subselect before. > Why would you want one? If only to do a "LIMIT 1" on it. But this is probably considered very ugly to exprienced DB users (I'm only recently self-taught on that subject). > And if you do want one, Louis-David, you can always use a temporary > table as previously described. I found another workaround to the problem, finally. Thanks -- Louis-David Mitterrand - ldm@apartia.org - http://www.apartia.org Your mouse has moved. Windows must be restarted for the change to take effect. Reboot now?