Re: NVL vs COALESCE

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Michael Glaesemann <grzm(at)myrealbox(dot)com>
Cc: Marcus Engene <mengpg(at)engene(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: NVL vs COALESCE
Date: 2005-11-28 23:19:27
Message-ID: 200511282319.jASNJRI00188@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Glaesemann wrote:
>
> On Nov 24, 2005, at 21:21 , Marcus Engene wrote:
>
> > When we're having an alias discussion, I'd really like to see NVL
> > in postgres. Not because of porting from oracle as much as just
> > spelling that without the reference manual is completely impossible.
>
> NVL: what a very unfortunate spelling. (NULL VaLue? NULL Valued
> Logic? Named Very Loosely? Someone help me here :) ) AFAICT, COALESCE
> is SQL standard, while NVL isn't. I think an index entry might be a
> good idea.

Agreed, documentation patch applied to HEAD and 8.1.X.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

Attachment Content-Type Size
unknown_filename text/plain 3.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-11-28 23:49:40 Re: Hashjoin startup strategy (was Re: Getting different number of results when using hashjoin on/off)
Previous Message Bruce Momjian 2005-11-28 22:45:03 Re: TRUNC vs. TRUNCATE