Re: Planning aggregates which require sorted or distinct - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Planning aggregates which require sorted or distinct
Date
Msg-id 1169288889.3776.50.camel@silverbirch.site
Whole thread Raw
In response to Re: Planning aggregates which require sorted or distinct  (Gavin Sherry <swm@alcove.com.au>)
List pgsql-hackers
On Sat, 2007-01-20 at 09:34 +1100, Gavin Sherry wrote:
> On Sat, 19 Jan 2007, Karen Hill wrote:
> 
> > Gavin Sherry wrote:
> > > Recenly, I've been researching and putting together a proposal for window
> > > functions.

Good news.

> > Implementing NULLS FIRST and NULLS LAST appears like another
> > challenging step to getting window functions wrapped up.  Has your
> > research lead you to any ideas on what your strategy for NULLS FIRST
> > and NULLS LAST likely would be?
> 
> Explicit handling of NULL is only in the Oracle extension to window
> functions. I will look at the core SQL functionality first -- maybe with
> the extension of 'LEAD' and 'LAG' because they are heavily utilitised by
> those using window functions.

NULLS FIRST | LAST is part of SQL:2003, specifically the definition of a
window over which an aggregate function can be applied contains a sort
specification list.

> Besides, Tom's been working on NULLS FIRST/LAST already.

For that very reason, I imagined.

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Markus Schiltknecht
Date:
Subject: Re: Planning aggregates which require sorted or distinct
Next
From: "Simon Riggs"
Date:
Subject: Re: Planning aggregates which require sorted or distinct