Re: coalesce with all nulls can only be assigned to - Mailing list pgsql-general

From Kevin Grittner
Subject Re: coalesce with all nulls can only be assigned to
Date
Msg-id 456D8EE4.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: coalesce with all nulls can only be assigned to  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: coalesce with all nulls can only be assigned to  (Richard Huxton <dev@archonet.com>)
Re: coalesce with all nulls can only be assigned to  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
>>> On Wed, Nov 29, 2006 at  1:38 PM, in message
<21909.1164829090@sss.pgh.pa.us>,
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>> Richard Huxton <dev@archonet.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?



pgsql-general by date:

Previous
From: Mark Jensen
Date:
Subject: Re: Including unique users in huge data warehouse in Postgresql...
Next
From: "Andrus"
Date:
Subject: Re: How to implement backup protocol