Re: coalesce with all nulls can only be assigned to

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Richard Huxton" <dev(at)archonet(dot)com>,<pgsql-general(at)postgresql(dot)org>
Subject: Re: coalesce with all nulls can only be assigned to
Date: 2006-11-29 19:45:09
Message-ID: 456D8EE4.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>> On Wed, Nov 29, 2006 at 1:38 PM, in message
<21909(dot)1164829090(at)sss(dot)pgh(dot)pa(dot)us>,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> Richard Huxton <dev(at)archonet(dot)com> wrote:
>>> It's the coalesce that has the problem, not the insert. The
coalesce is
>>> deciding that it's working on text, and so returns text.
>
>> It seems like maybe it would be worth overloading the coalesce
method
>> to handle this particular case differently.
>
> And do what? The only information you have is that all the inputs
are
> of unknown type.

I know this is naive, but, what is the type information of the bare
null? Could that be used?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2006-11-29 19:49:47 Re: How to implement backup protocol
Previous Message Andrus 2006-11-29 19:43:56 Re: How to implement backup protocol