Re: greatest/least semantics different between oracle and postgres

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ben <bench(at)silentmedia(dot)com>, "PostgreSQL General ((EN))" <pgsql-general(at)postgresql(dot)org>
Subject: Re: greatest/least semantics different between oracle and postgres
Date: 2007-06-30 15:27:02
Message-ID: 200706301527.l5UFR2q29395@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Gregory Stark wrote:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> > GREATEST/LEAST aren't in the spec, so there's not much help there.
> >
> > Except ... if they ever do get added to the spec, what do you think
> > the spec will say? The odds it'd contradict Oracle seem about nil.
>
> Fwiw even in the min/max/sum case the spec is moving away from having
> aggregates ignore NULL values. You now get a warning in Oracle if your
> aggregate includes any NULL inputs.

How does Oracle's new behavior relate to the standard moving?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Oleg Bartunov 2007-06-30 15:30:56 Re: stem & tsearch2, want different stemmed words
Previous Message Dave Page 2007-06-30 15:14:05 Re: postgressqlnot support inwindows 2000