Re: COALESCE and NULLIF semantics

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>,"Sam Mason" <sam(at)samason(dot)me(dot)uk>
Subject: Re: COALESCE and NULLIF semantics
Date: 2009-09-11 18:01:02
Message-ID: 4AAA4A0E020000250002AD05@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> I was thinking of changing what is currently done, for example,
>> here:
>
>> newc->coalescetype = select_common_type(pstate, newargs,
>> "COALESCE", NULL);
>
>> Is that so late as you say, or is there a reason that can't work?
>
> It's what happens afterwards that's the problem --- try it and see.

Anything in particular I should test or be looking for, or will the
error of my ways be glaringly obvious on any usage?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-09-11 18:10:44 Re: COALESCE and NULLIF semantics
Previous Message Tom Lane 2009-09-11 17:50:35 Re: COPY enhancements