Re: Hmm, nodeUnique doesn't really support backwards scan too well

From: "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Hmm, nodeUnique doesn't really support backwards scan too well
Date: 2008-08-05 23:00:10
Message-ID: 3073cc9b0808051600y67ab8eees38a603085bf9ed07@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 8/5/08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > I've never seen anyone scan backwards like this at all in practical use.
>
> > I knew it was possible, but never seen it done.
>
> > It seems entirely probable nobody else has either. It's a PostgreSQL
> > extension, so people arriving from outside don't even know it exists,
>
> Say again? Both the SCROLL option to DECLARE CURSOR and FETCH PRIOR are
> straight out of the SQL92 spec.
>

i think Simon is talking about DISTINCT ON

--
regards,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Guayaquil - Ecuador
Cel. (593) 87171157

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Simon Riggs 2008-08-06 04:14:09 Re: Hmm, nodeUnique doesn't really support backwards scan too well
Previous Message Tom Lane 2008-08-05 22:40:08 Re: Hmm, nodeUnique doesn't really support backwards scan too well