Re: select random order by random

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Richard Huxton" <dev(at)archonet(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Lee Keel" <lee(dot)keel(at)uai(dot)com>, piotr_sobolewski <piotr_sobolewski(at)o2(dot)pl>, pgsql-general(at)postgresql(dot)org
Subject: Re: select random order by random
Date: 2007-11-01 20:44:54
Message-ID: dcc563d10711011344m21763aeu26820e9f9e8198@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/1/07, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
> On Thu, Nov 01, 2007 at 02:22:58PM -0400, Tom Lane wrote:
> > > SELECT random() FROM generate_series(1, 10) ORDER BY random();
> > > SELECT random() AS foo FROM generate_series(1, 10) ORDER BY foo;
> >
> > (BTW, this is not the planner's fault; the collapsing of the two
> > targetlist entries into one happens in the parser.)
>
> Something twigged telling me that in fact the latter expression is not
> in standard SQL but a (very common) extension. A <sort key> is clearly
> indicated to be a <value expression> with no indication anywhere that
> column aliases are allowed here (though that may be in the common rules
> somewhere).

Well, the standard way I know if is to use column numbers. i.e.:

select random() from generate_series(1,10) order by 1

That I'm pretty sure IS in the standard. Don't see why column aliases
would be disallowed. It's not like the where clause where the select
field doesn't exist when it fires. The select field list does exist
when order by fires, so referring to it makes sense.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2007-11-01 20:56:28 Re: [GENERAL] Abbreviation list
Previous Message Martijn van Oosterhout 2007-11-01 20:35:35 Re: select random order by random